CachingCostBalancerStrategy does not load multiple segments having granularity ALL
Open
Area - Segment Balancing/Coordination
- Dominant language
- Java
- Stars
- 14.1k
- Forks
- 3.8k
- Avg merge
- 2d 58m
- Merged PRs (30d)
- 233
Description
### Affected Version
All
### Description
Load example data twice with different datasource name with `ALL` segment granularity, segment for first datasource will be loaded but other segment will not be loaded as this strategy will calculate Infinite cost for loading it. This is not a problem with `cost` balancer strategy.
Contributor guide
Research direction
Reproduce the case by loading the same example data twice under different datasource names with ALL segment granularity. Start in CachingCostBalancerStrategy and trace why the second segment receives infinite loading cost; done means both datasource segments load, matching the behavior of the cost balancer strategy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100