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

allocator: refactor to accept StorePool on rebalance #91968

Conversation

AlexTalks
Copy link
Contributor

WIP

Depends on #91461, #91965, #91941.

Part of #91570.

Release Note: None

This change refactors the usage of `StorePool` in the allocator to a new
interface, `AllocatorStorePool`, in order to be able to utilize a store
pool with overriden liveness to properly evaluate decommission
pre-flight checks.

Part of cockroachdb#91570.

Release note: None
While previously the allocator only evaluated using liveness obtained
from gossip, this change introduces a new `OverrideStorePool` struct
which can be used to override the liveness of a node for the purposes of
evaluating allocator actions and targets.  This `OverrideStorePool` is
backed by an existing actual `StorePool`, which retains the majority of
its logic.

Depends on cockroachdb#91461.

Part of cockroachdb#91570.

Release note: None
This change adds methods to be to evaluate allocator actions and targets
utilizing a passed-in `StorePool` object, allowing for the allocator to
consider potential scenarios rather than those simply based on the
current liveness.

Depends on cockroachdb#91461, cockroachdb#91965.

Part of cockroachdb#91570.

Release note: None
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@AlexTalks
Copy link
Contributor Author

abandoned, this has been subsumed by other/better PRs.

@AlexTalks AlexTalks closed this Jan 18, 2023
@AlexTalks AlexTalks deleted the dpf_allocator_refactor_rebalances branch January 18, 2023 17:28
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