-
Notifications
You must be signed in to change notification settings - Fork 552
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
storage: make input stream buffer size configurable #3412
Labels
Comments
jcsp
added
kind/enhance
New feature or request
area/storage
area/cloud-storage
Shadow indexing subsystem
labels
Jan 7, 2022
jcsp
added a commit
to jcsp/redpanda
that referenced
this issue
Jan 10, 2022
Fixes: redpanda-data#3412 Signed-off-by: John Spray <jcs@vectorized.io>
jcsp
added a commit
to jcsp/redpanda
that referenced
this issue
Jan 10, 2022
Fixes: redpanda-data#3412 Signed-off-by: John Spray <jcs@vectorized.io>
jcsp
added a commit
to jcsp/redpanda
that referenced
this issue
Jan 10, 2022
Fixes: redpanda-data#3412 Signed-off-by: John Spray <jcs@vectorized.io>
jcsp
added a commit
to jcsp/redpanda
that referenced
this issue
Jan 10, 2022
Fixes: redpanda-data#3412 Signed-off-by: John Spray <jcs@vectorized.io> (cherry picked from commit 05e8c99)
jcsp
added a commit
to jcsp/redpanda
that referenced
this issue
Jan 11, 2022
Fixes: redpanda-data#3412 Signed-off-by: John Spray <jcs@vectorized.io> (cherry picked from commit 05e8c99)
Backporting to 21.11.x here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The default 128kiB is too high for systems with high partition counts or small segment sizes (therefore may segments). Each partition can have several segments open (especially during compaction, shadow indexing upload, multiple readers at different offsets).
Something like 16KiB is more appropriate when the partition count is high.
We should make this configurable, and possibly also auto-adjust the buffer size if the partition count is above a certain amount.
Related: #3398, in which the memory footprint of a partition is dominated by
number_of_open_segments * input_stream_buffer_size
. The safety check should probably be parametrized on the input stream size. This will remain true until the reader code is re-worked to avoid holding readers open for every segment.The text was updated successfully, but these errors were encountered: