linkedin / linkedin/dr-elephant
TonyMetricsAggregator should calculate delay
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 839
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we don't calculate delay for TonY jobs (neither does the SparkMetricsAggregator). It may be useful to calculate the delay for Tony jobs. (However, container delay metrics can probably be better calculated at the RM level -- delay between container request and container allocated.)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating TonyMetricsAggregator and compare its current behavior with SparkMetricsAggregator, especially any existing delay-related metrics. Clarify which TonY delay is intended, then define completion as calculating and exposing that delay consistently; the issue notes that container request-to-allocation delay may belong at the RM level instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100