Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NSFS | Prevent concurrent UploadPart with different data #8018

Open
romayalon opened this issue May 7, 2024 · 0 comments
Open

NSFS | Prevent concurrent UploadPart with different data #8018

romayalon opened this issue May 7, 2024 · 0 comments
Labels
NS-FS Type: Technical Debt Known technical gaps left in the system
Milestone

Comments

@romayalon
Copy link
Contributor

romayalon commented May 7, 2024

Environment info

  • NooBaa Version: 5.15
  • Platform: rhel+gpfs+nsfs

Actual behavior

  1. While @guymguym and I looked at observed in noobaa log as "cancelled due to ctime change" actual upload didn't fail  #7833 and NC | UploadPart | finish_upload | stat(part-{num}) should not check ctime due to concurrency part uploads of the same part. #8017, a need to define better the concurrent NSFS UploadPart bahevior raised.
    Few examples -
  2. Concurrent UploadPart calls, partNumber equals (Sort of a retry), uploadId equals.
  3. Concurrent UploadPart calls, partNumber differs, uploadId equals.
  4. Conccurent UploadPart call and Complete multipart upload call, upload id equals.

Expected behavior

  1. Having a well defined behavior of conccurent scenarios.

Steps to reproduce

  1. NA

More information - Screenshots / Logs / Other output

@romayalon romayalon added the NS-FS label May 7, 2024
@guymguym guymguym added the Type: Technical Debt Known technical gaps left in the system label May 8, 2024
@guymguym guymguym added this to the 5.16.z milestone May 8, 2024
@guymguym guymguym changed the title NSFS | Conccurency UploadPart behavior research NSFS | Prevent concurrent UploadPart with different data May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NS-FS Type: Technical Debt Known technical gaps left in the system
Projects
None yet
Development

No branches or pull requests

2 participants