-
Notifications
You must be signed in to change notification settings - Fork 1k
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
when pod CrashLoopBackOff,the job status should be failed #436
Comments
Fair point, In this case we should have set a fixed number of retry, and mark it fail to prevent useless running. |
@davidstack Can you try with #412 ? |
@hzxuzhonghu after set the maxRetry, it has the same problem. apiVersion: batch.volcano.sh/v1alpha1
kind: Job
metadata:
name: tensorflow-benchmark
labels:
"volcano.sh/job-type": "Tensorflow"
spec:
minAvailable: 3
schedulerName: volcano
maxRetry: 2
plugins:
env: []
svc: []
|
/assign @hzxuzhonghu |
ok, let me investigate. |
@davidstack It is because when crashloopback, the pod phase is still running. The RestartPolicy of pod is ALways by default. |
To enhance this scenario, in volcano we should prevent the endless and meaningless retries. |
Hello 👋 Looks like there was no activity on this issue for last 90 days. |
Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗 |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
i test create tf-sample ,when i got this status
but the job status is running
What you expected to happen:
when one task failed, the job should in failed status
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: