Per region DD metrics/logs
- Dominant language
- C++
- Stars
- 16.7k
- Forks
- 1.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 126
Description
For clusters with HA (aka multi-region) configuration, it's hard to reason about Data Distributor as most of the metrics (in status) and logs report stats for all of the regions together. `TeamCollectionInfo` is reported per region, we could do the same probably. Although, instead of having a boolean of `primary`, it's good to have the region name given in the configuration.
Contributor guide
Research direction
Start by tracing Data Distributor's status metrics and logs for HA or multi-region clusters, then compare their reporting with the per-region TeamCollectionInfo path. Identify where the configured region name is available and define completion as region-specific metrics and logs that label each region by name rather than aggregating all regions or using only a primary boolean.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, distributed-systems, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100