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

backupccl: bump file buffer size to 128MiB but with dynamic growth #75988

Merged

Conversation

adityamaru
Copy link
Contributor

This change bumps the bulkio.backup.merge_file_buffer_size value
to 128MiB from its previous default of 16MiB. This setting determines
the maximum byte size of ssts that can be buffered during a backup
before the queue needs to be flushed.

Instead of always using 128MiB, we incrementally grow the
boundaccount associated with the backup processor from 32MiB
to the cluster settings value, in increments of 32MiB.

Release note (sql change): bulkio.backup.merge_file_buffer_size
default value has been changed from 16MiB to 128MiB. This value determines
the maximum byte size of SSTs that we buffer before forcing a flush
during a backup.

@adityamaru adityamaru requested review from dt and a team February 3, 2022 23:06
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@adityamaru adityamaru force-pushed the incrementally-reserve-file-buf branch 2 times, most recently from f0155e0 to 0545bcc Compare February 4, 2022 21:48
This change bumps the `bulkio.backup.merge_file_buffer_size` value
to 128MiB from its previous default of 16MiB. This setting determines
the maximum byte size of ssts that can be buffered during a backup
before the queue needs to be flushed.

Instead of always using 128MiB, we incrementally grow the
boundaccount associated with the backup processor from 32MiB
to the cluster settings value, in increments of 32MiB.

Release note (sql change): `bulkio.backup.merge_file_buffer_size`
default value has been changed from 16MiB to 128MiB. This value determines
the maximum byte size of SSTs that we buffer before forcing a flush
during a backup.
@adityamaru adityamaru force-pushed the incrementally-reserve-file-buf branch from 0545bcc to 3f9f470 Compare February 7, 2022 22:10
@adityamaru
Copy link
Contributor Author

adityamaru commented Feb 8, 2022

bazel failure is unrelated, timeout in [pkg/gossip/gossip_test_/gossip_test]

TFTR!

bors r=dt

@craig
Copy link
Contributor

craig bot commented Feb 8, 2022

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Feb 8, 2022

Build succeeded:

@craig craig bot merged commit 844ac13 into cockroachdb:master Feb 8, 2022
@adityamaru adityamaru deleted the incrementally-reserve-file-buf branch February 8, 2022 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants