-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Restore chunksize of 512kb on recovery and remove configurability #15235
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
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.
512 * 1024 👅
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.
new ByteSizeValue("512kb").bytes() ![]()
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.
fucking returns a stupid long I don't wanna cast
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.
bytesAsInt()
|
Production code LGTM. I left some concerns about the testing change. |
This commit restores the chunk size of 512kb lost in a previous but unreleased refactoring. At the same time it removes the configurability of: * `indices.recovery.file_chunk_size` - now fixed to 512kb * `indices.recovery.translog_ops` - removed without replacement * `indices.recovery.translog_size` - now fixed to 512kb * `indices.recovery.compress` - file chunks are not compressed due to lucene's compression but translog operations are. The compress option is gone entirely and compression is used where it makes sense. On sending files of the index we don't compress as we rely on the lucene compression for stored fields etc. Relates to elastic#15161
09bd792 to
37b60bd
Compare
|
@bleskes I had to add one more commit - can you take a quick look? |
|
LGTM |
…for closing streams to not hide original exception
|
@bleskes I refined this change one more time to allow tests to override the chunksize which I think is a good tool to have (pkg private setter) and I also fixed the stream closing issue. I think it's ready now. Do you wanna take one more look? |
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.
add comment about what this is not final (i.e., for testing)
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 setter has a comment
|
LGTM (better than before). left some minor optional suggestions. |
Restore chunksize of 512kb on recovery and remove configurability
Updated document as per this change : elastic#15235
Updated document as per this change : #15235
Updated document as per this change : #15235
Updated document as per this change : #15235
Updated document as per this change : #15235
This commit restores the chunk size of 512kb lost in a previous but unreleased
refactoring. At the same time it removes the configurability of:
indices.recovery.file_chunk_size- now fixed to 512kbindices.recovery.translog_ops- removed without replacementindices.recovery.translog_size- now fixed to 512kbindices.recovery.compress- file chunks are not compressed due to lucene's compression but translog operations are.The compress option is gone entirely and compression is used where it makes sense. On sending files of the index
we don't compress as we rely on the lucene compression for stored fields etc.
Relates to #15161