Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
go/vt/mysqlctl: add configurable read buffer to builtin backups #12073
go/vt/mysqlctl: add configurable read buffer to builtin backups #12073
Changes from 6 commits
1abc241
3404450
2c649a8
6d43daa
4a7b8a6
2790b51
80bd81b
0db048d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
These have nothing to do with block device block sizes, right? If so, IMO it would be a little more clear to say chunks instead of blocks in this context. Or it may be even more clear/precise to say that we use a buffer of this size each time that we read/write backup data from disk?
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 current behavior is that we use the same 2 MiB buffer when writing files to disk during restores or writing to backupstorage during backups.
Backupstorage may or may not go directly to disk, so I think it makes sense to decouple these buffers to they can be tuned independently.
I think it would be even better if builtinbackup didn't do any buffering when reading to or writing from backupstorage, and instead would be better to let each backupstorage engine decide how to handle read/write buffering, maybe with tunable flags.
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.
why was this moved from builtin to this file? It's not actually used by xtrabackupengine AFAICT.
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.
It is used!
vitess/go/vt/mysqlctl/xtrabackupengine.go
Line 327 in da69672
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.
ah it was already being used. And it is no longer used in builtin. 👍