Completely disable cachingCost balancer strategy #14798
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
cachingCost
has been deprecated in #14484 and is not advised to be used in production clusters as it may cause usage skew across historicals which the coordinator is unable to rectify. This PR completely disablescachingCost
strategy as it has now been rendered redundant due to recent performance improvements made tocost
strategy.Changes
cachingCost
strategyDisabledCachingCostBalancerStrategyFactory
for the time being so that we can give a proper error message before falling back toCostBalancerStrategy
. This will be removed in subsequent releases.CachingCostBalancerStrategy
and related classes for testing and benchmarking purposes.DiskCostBalancerStrategy
.Release note
cachingCost
balancer strategy is now disabled and cannot be used in a Druid cluster. UsingcachingCost
falls back tocost
balancer strategy.