Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Report number of job restarts as a metric #122

Open
s-vitaliy opened this issue Aug 12, 2024 · 1 comment
Open

[FEATURE] Report number of job restarts as a metric #122

s-vitaliy opened this issue Aug 12, 2024 · 1 comment
Labels
code/new-feature New feature or request

Comments

@s-vitaliy
Copy link
Contributor

s-vitaliy commented Aug 12, 2024

Description

We need to track the streams that can be stopped due to exhaustion of a backoff limit.

Possible solution

On every job change event get number of pods in failed state and calculate metrics based on this value.

Alternatives

Listen to pods events and store mapping job_id <--> failed_pods_count in memory.

Context

The backoffLimit algorithm is explained here: https://kubernetes.io/docs/concepts/workloads/controllers/job/#pod-backoff-failure-policy

@s-vitaliy s-vitaliy added the code/new-feature New feature or request label Aug 12, 2024
@s-vitaliy s-vitaliy self-assigned this Aug 12, 2024
@s-vitaliy s-vitaliy added this to Arcane Aug 12, 2024
@s-vitaliy
Copy link
Contributor Author

Creating a metric like that seems to be not so easy. We need to investigate how the Kubernetes Job Controller actually manages the backoff counter. Consequently, the task size has been upgraded to XL and the priority has been decreased.

@s-vitaliy s-vitaliy moved this to Backlog in Arcane Aug 14, 2024
@s-vitaliy s-vitaliy removed their assignment Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code/new-feature New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant