We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Vitess-operator can be smarter about when it should spawn a VTOrc instance. If a shard only has external tablets, then we don't require a VTOrc.
The text was updated successfully, but these errors were encountered:
Hmm.. looking at the example from vitess repo https://github.com/vitessio/vitess/blob/main/examples/operator/201_customer_tablets.yaml#L70
It looks like we are running vtorc only for the commerce keyspace and not for the customer keyspace. Is this by design? A separate vtorc per keyspace?
Can people run a single vtorc across many keyspace/shards? And if they do, is it still possible to exclude external tablets?
Sorry, something went wrong.
No branches or pull requests
Description
The Vitess-operator can be smarter about when it should spawn a VTOrc instance. If a shard only has external tablets, then we don't require a VTOrc.
The text was updated successfully, but these errors were encountered: