You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the cluster is scaled down from 3 nodes to 1, when the syncers are created it starts with the nodes that are not master, with the nodes that do not exist anymore. So the first syncer fails and will never run the master syncer. Check the code here.
The text was updated successfully, but these errors were encountered:
* Support longer entity names with more character choices.
Cluster, keyspace, cell, and backup location names can now be longer and
can contain more characters.
- VitessCluster names can be up to 63 chars and must match
the regex `^[a-z0-9]([a-z0-9-.]*[a-z0-9])?$`.
- Keyspace and backup location names can be anything allowed
as a k8s label value: up to 63 chars, matching the regex
`^[A-Za-z0-9]([A-Za-z0-9-_.]*[A-Za-z0-9])?$`.
- Cell names are similar, but cannot contain `-` because Vitess doesn't
support `-` in cell names due to the tablet alias format.
Signed-off-by: Anthony Yeh <[email protected]>
* Explicitly check validity of MaxLength.
Signed-off-by: Anthony Yeh <[email protected]>
* Deprecate old Join functions without constraints.
Signed-off-by: Anthony Yeh <[email protected]>
If the cluster is scaled down from 3 nodes to 1, when the syncers are created it starts with the nodes that are not master, with the nodes that do not exist anymore. So the first syncer fails and will never run the master syncer. Check the code here.
The text was updated successfully, but these errors were encountered: