Skip to content
This repository has been archived by the owner on Jan 9, 2020. It is now read-only.

Adding restart policy fix for v2 #303

Merged
merged 1 commit into from
May 25, 2017
Merged

Conversation

foxish
Copy link
Member

@foxish foxish commented May 25, 2017

Fixes #302

cc @apache-spark-on-k8s/contributors

@foxish
Copy link
Member Author

foxish commented May 25, 2017

rerun integration test please

Copy link

@ash211 ash211 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mccheah
Copy link

mccheah commented May 25, 2017

Looks fine. Merging.

@mccheah mccheah merged commit b84cb66 into branch-2.1-kubernetes May 25, 2017
@mccheah
Copy link

mccheah commented May 25, 2017

Does this need to be on executors also?

@mccheah mccheah deleted the fix-restart-policy branch May 25, 2017 17:44
@foxish
Copy link
Member Author

foxish commented May 25, 2017

Hmm.. the executors restart and try to reconnect, which is recovery behavior we want in that case. I don't think there is a reason to prevent executor pods restarting after errors. If it is a transient error, it will eventually succeed, and if it isn't, we should fail the job after a threshold.

cc @varunkatta

foxish added a commit that referenced this pull request Jul 24, 2017
ifilonenko pushed a commit to ifilonenko/spark that referenced this pull request Feb 26, 2019
ifilonenko pushed a commit to ifilonenko/spark that referenced this pull request Feb 26, 2019
puneetloya pushed a commit to puneetloya/spark that referenced this pull request Mar 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants