-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Topo lookup tablet type #18777
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
Topo lookup tablet type #18777
Changes from all commits
7e34de9
6bbb76e
2f64815
8b7aa22
0a36591
07ff616
980ae08
b9a0213
d987ab5
10a8fab
1472eaf
be6b619
3dd2326
bc3087d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -174,7 +174,8 @@ Flags: | |
| --init-db-name-override string (init parameter) override the name of the db used by vttablet. Without this flag, the db name defaults to vt_<keyspacename> | ||
| --init-keyspace string (init parameter) keyspace to use for this tablet | ||
| --init-shard string (init parameter) shard to use for this tablet | ||
| --init-tablet-type string (init parameter) tablet type to use for this tablet. Valid values are: PRIMARY, REPLICA, SPARE, and RDONLY. The default is REPLICA. | ||
| --init-tablet-type string (init parameter) tablet type to use for this tablet. Valid values are: REPLICA, RDONLY, and SPARE. The default is REPLICA. | ||
| --init-tablet-type-lookup (Experimental, init parameter) if enabled, uses tablet alias to look up the tablet type from the existing topology record on restart and use that instead of init-tablet-type. This allows tablets to maintain their changed roles (e.g., RDONLY/DRAINED) across restarts. If disabled or if no topology record exists, init-tablet-type will be used. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @sbaker617 I feel this comment should be updated so Vitess users understand this feature won't work on Vitess operator deployments, where tablet records are not left around in the topo I think this current description may lead to those users trying this and believing there is a bug
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @timvaillancourt what would you like to see included in the message to best guide
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd rather not get into specifics like that. The operator's pruning behavior is configurable. There's a good chance that the replacement has a different alias (e.g. in another AZ) though too. But these are implementation details and examples of where the record would not be found and thus |
||
| --init-tags StringMap (init parameter) comma separated list of key:value pairs used to tag the tablet | ||
| --init-timeout duration (init parameter) timeout to use for the init phase. (default 1m0s) | ||
| --jaeger-agent-host string host and port to send spans to. if empty, no tracing will be done | ||
|
|
||
mattlord marked this conversation as resolved.
Show resolved
Hide resolved
|
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'm not sure how accurate or helpful this is in the end. I'm fine leaving it though.