-
Notifications
You must be signed in to change notification settings - Fork 81
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
Empty block objects constructed by upload-bin
command
#3630
Comments
Uploader strategy (reupload blocks starting from the start of the oldest half-uploaded batch of blocks) with combination of empty blocks uploading leads to the fact that there can be multiple block objects corresponding to a single height (one object is a non-empty block, and another object is an empty block). Logs provided by @AliceInHunterland:
It leads to invalid NeoFSBlockFetcher behaviour in "index files disabled" mode since search over range of blocks gives more results than expected:
|
In case of uploading retry already drained bin buffer is return in `bw .Bytes`,which leads to empty block uploading. Close #3630 Signed-off-by: Ekaterina Pavlova <[email protected]> Signed-off-by: Ekaterina Pavlova <[email protected]>
In case of uploading retry already drained bin buffer is returned in `bw.Bytes`, which leads to empty block uploading. Close #3630 Signed-off-by: Ekaterina Pavlova <[email protected]>
In case of uploading retry already drained bin buffer is returned in `bw.Bytes`, which leads to empty block uploading. Close #3630 Signed-off-by: Ekaterina Pavlova <[email protected]>
Current Behavior
SkipIndexFilesSearch: true
Expected Behavior
not empty block object
Context
upload-bin
command uploading blocks as objects.The text was updated successfully, but these errors were encountered: