-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
RFC: vttablet breaking changes #6345
Milestone
Comments
It turns out that |
sougou
added a commit
to planetscale/vitess
that referenced
this issue
Jun 26, 2020
Ref vitessio#6345 We need to allow this flag until existing users can migrate out. Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
The following were undocumented, and likely unused behaviors. These are changing in #6461:
|
Fixed in #6461 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an expansion of #6131 to mainly highlight some changes that are not backward compatible. These decisions were based on our perception of how vitess is currently used, with the hope that they should not materially affect any existing deployments.
init_keyspace
,init_shard
andinit_tablet_type
will be made mandatory. The flow where you could issue avtctlclient InitTablet
and then invoke vttablet without those init parameters will not be supported.InitTablet
andUpdateTabletAddrs
will also be deprecated.demote_master_type
is deprecated: Now thatinit_tablet_type
is mandatory, that value can act as thedemote_master_type
. There is no need for a separate flag.enable_replication_watcher
fromdisable_active_reparaents
. Currently, vttablet fixes replication only ifenable_replication_watcher
is true anddisable_active_reparents
is false. We will change this behavior to depend only on thedisable_active_reparents
flag.The text was updated successfully, but these errors were encountered: