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.

Sign up for GitHub

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

Jump to bottom

Add doomed-to-failure detection to Job #25254

Closed
soltysh opened this issue May 6, 2016 · 8 comments
Closed

Add doomed-to-failure detection to Job #25254

soltysh opened this issue May 6, 2016 · 8 comments
Assignees
@soltysh
Labels
area/batch priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@soltysh
Copy link
Contributor

soltysh commented May 6, 2016

Per this comment we want infant-mortality detection to Job, with no knob, and backoff in the event of failures in the middle of Job execution (#2529).
@soltysh
Copy link
Contributor Author

soltysh commented May 6, 2016

@bgrant0607 mind assigning this one to me

@soltysh soltysh mentioned this issue May 6, 2016
Closed
@bgrant0607 bgrant0607 added priority/backlog Higher priority than priority/awaiting-more-evidence. area/controller-manager team/control-plane labels May 6, 2016
@bgrant0607
Copy link
Member

cc @erictune @Kargakis @janetkuo

@derekwaynecarr
Copy link
Member

Can we avoid calling it by this name?

@pmorie
Copy link
Member

pmorie commented May 6, 2016

please

@derekwaynecarr
Copy link
Member

Maybe premature failure detection, where failure window is defined as X

@soltysh
Copy link
Contributor Author

soltysh commented May 9, 2016

The name is an open topic, I don't mind picking a different one.

@erictune erictune changed the title Add infant-mortality detection to Job Add doomed-to-failure detection to Job May 9, 2016
@erictune
Copy link
Member

erictune commented May 9, 2016

Renamed "doomed-to-failure"

@erictune erictune added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels May 10, 2016
@erictune
Copy link
Member

Closing in favor of #30243

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@soltysh soltysh

Labels
area/batch priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@pmorie @soltysh @derekwaynecarr @bgrant0607 @erictune