Skip to content
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

kvtenant: expose NodesStatusServer #65049

Closed
wants to merge 3 commits into from

Conversation

otan
Copy link
Contributor

@otan otan commented May 12, 2021

See individual commits for details.

Currently on hold.

Refs #54252, #47900

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@otan otan changed the title [WIP] kvtenant: expose NodeStatusServer [WIP] kvtenant: expose NodesStatusServer May 12, 2021
@otan otan force-pushed the attr_fix_v2 branch 2 times, most recently from 9f7be5a to 4d4147b Compare May 12, 2021 08:01
otan added 3 commits May 14, 2021 10:00
NodesStatusServer is now exposed as an interface in kvtenant, with an
implementation in kvtenantccl reading node statuses off KV using the
InternalClient interface.

Release note: None
Now that kvtenant.Connector implements the NodesStatusServer interface,
we can remove the OptionalNodesStatusServer item and use the
kvtenant.Connector object directly for tenant instances.

Release note: None
Tests multi-region cluster with tenants.

Only SHOW REGIONS FOR CLUSTER works at this stage.

Release note: None
@otan otan changed the title [WIP] kvtenant: expose NodesStatusServer kvtenant: expose NodesStatusServer May 14, 2021
@otan otan closed this May 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants