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

loqrecovery: add replica info collector #93040

Closed
aliher1911 opened this issue Dec 5, 2022 · 1 comment · Fixed by #93157
Closed

loqrecovery: add replica info collector #93040

aliher1911 opened this issue Dec 5, 2022 · 1 comment · Fixed by #93157
Assignees
Labels
A-kv-replication Relating to Raft, consensus, and coordination. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Comments

@aliher1911
Copy link
Contributor

aliher1911 commented Dec 5, 2022

Add implementation of collection rpc in Admin as per RFC:

Collection should do a best effort collection of range descriptor metadata about all ranges. This full or partial info should be streamed back to caller.
Collection should use fanout to nodes discovered via gossip to collect replica info and stream info back to caller.
It should tolerate any partial failures and send only available info.

Depends on changes to plan protobuf definition in #93037

Part of #77273

Jira issue: CRDB-22129

Epic CRDB-14205

@aliher1911 aliher1911 added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-kv-replication Relating to Raft, consensus, and coordination. T-kv-replication labels Dec 5, 2022
@blathers-crl
Copy link

blathers-crl bot commented Dec 5, 2022

cc @cockroachdb/replication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-kv-replication Relating to Raft, consensus, and coordination. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant