-
Notifications
You must be signed in to change notification settings - Fork 492
Fix azure multipart upload data corruption #5919
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
Conversation
94b4d85 to
f034ae5
Compare
|
|
f034ae5 to
0e2d1af
Compare
guilload
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix looks good. I left some minor comments.
0802ea2 to
ec54eff
Compare
Blocks were added to BlockList in completion order rather than sequential order, causing data corruption. Zero pad block IDs and sort before committing to ensure correct blob reconstruction. Also improve the existing test that was only checking file, the test would fail on main if integrity check was turned on. This PR passes the unit test, also has been runnin in for last two days in production without data corruption, prior to this PR - split was getting corrupted every 45 minutes.
ec54eff to
c71bda2
Compare
guilload
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved! Thanks @shrijeet.
Description
Blocks were added to BlockList in completion order rather than sequential order, causing data corruption. Zero pad block IDs and sort before committing to ensure correct blob reconstruction.
Also improve the existing test that was only checking file, the test would fail on main if integrity check was turned on.
How was this PR tested?
This PR passes the unit test, also has been runnin in for last two days in production without data corruption, prior to this PR - split was getting corrupted every 45 minutes.