-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
changefeedccl: Break gossip dependency #101096
Conversation
Break the dependency on Gossip library which was used to determine the number of nodes in the cluster in order to limit scanner concurrency. Instead, rely on the range descriptors in order to determine how many nodes host the ranges that need to be scanned. Fixes cockroachdb#47971 Release note: None
It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR? 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @miretskiy and @shralex)
pkg/ccl/changefeedccl/kvfeed/scanner.go
line 254 at r1 (raw file):
// getRangesToProcess returns the list of ranges covering input list of spans. // Returns the number of nodes that are leaseholders for those spans.
nit: This is not necessarily the number of leaseholders, right? it.Desc().InternalReplicas
returns all the nodes hosting replicas.
Do you feel strongly on this (and force rerunning CI)? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not feel strongly. Feel free to merge.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @miretskiy and @shralex)
bors r+ |
Build succeeded: |
Break the dependency on Gossip library which was
used to determine the number of nodes in the cluster in order to limit scanner concurrency.
Instead, rely on the range descriptors in order
to determine how many nodes host the ranges that
need to be scanned.
Fixes #47971
Release note: None