Resource Groups: Emit metrics that could be used by external schedulers
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
Determine what kind of metrics should be emitted so that external resource schedulers (e.g., [HPA](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/), [KEDA](https://keda.sh/), etc.) can add or remove compute resources based on demand. For example, external compactor scaling based on compaction queues. Or, scaling the number of ScanServers based on current ScanServer load and number of clients performing scans.
Contributor guide
Research direction
Start by reviewing the issue's examples involving external compaction scaling, ScanServer load, scan clients, HPA, and KEDA. Determine which demand signals external schedulers would need and how completion would be judged; the payload names no source files, tests, or entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100