-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
[3.5] add experimental-snapshot-catchup-entries flag #17808
[3.5] add experimental-snapshot-catchup-entries flag #17808
Conversation
Skipping CI for Draft Pull Request. |
Signed-off-by: Siyuan Zhang <[email protected]>
d544ae4
to
7a8d28e
Compare
/retest |
7a8d28e
to
2fa2272
Compare
@@ -302,6 +302,7 @@ func newConfig() *config { | |||
fs.BoolVar(&cfg.ec.ExperimentalMemoryMlock, "experimental-memory-mlock", cfg.ec.ExperimentalMemoryMlock, "Enable to enforce etcd pages (in particular bbolt) to stay in RAM.") | |||
fs.BoolVar(&cfg.ec.ExperimentalTxnModeWriteWithSharedBuffer, "experimental-txn-mode-write-with-shared-buffer", true, "Enable the write transaction to use a shared buffer in its readonly check operations.") | |||
fs.UintVar(&cfg.ec.ExperimentalBootstrapDefragThresholdMegabytes, "experimental-bootstrap-defrag-threshold-megabytes", 0, "Enable the defrag during etcd server bootstrap on condition that it will free at least the provided threshold of disk space. Needs to be set to non-zero value to take effect.") | |||
fs.Uint64Var(&cfg.ec.SnapshotCatchUpEntries, "experimental-snapshot-catchup-entries", cfg.ec.SnapshotCatchUpEntries, "(WARNING: Use this flag with caution!) Number of entries for a slow follower to catch up after compacting the raft storage entries.") |
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.
I think we should add similar "WARNING: Use this flag with caution!" for the main branch as well.
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.
Can you provide more context why you think that? The original PR added the warning because we are backporting a feature just for testing, and we didn't want to make it visible to users.
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 original PR added the warning because we are backporting a feature just for testing
I don't think it's a good idea to add a user-facing flag but only supposed to be used by test. #17808 (comment)
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.
This is only a test only backport, but the original flag was introduced in #15033 with broader set of motivations. I'm mentioning it to ensure we discuss it before we add the warning on the main branch.
Please signoff the commit |
9047d40
to
3b4f255
Compare
Signed-off-by: Siyuan Zhang <[email protected]>
3b4f255
to
c391d69
Compare
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.
#17752
This is import prerequisite to verify that in a mixed version cluster, the follower receives a snapshot that has the correct schema for that version.
Did not add the flag to help file so that it is a hidden flag that only is used for testing.