Skip to content

[SPARK-13852][YARN]handle the InterruptedException caused by YARN HA switch #11692

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

Closed
WangTaoTheTonic wants to merge 2 commits into from
Closed

[SPARK-13852][YARN]handle the InterruptedException caused by YARN HA switch #11692

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9d6de23
handle the InterruptedException caused by YARN HA switch
WangTaoTheTonic Mar 14, 2016
27203d8
put it in a seperate case
WangTaoTheTonic Mar 14, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
put it in a seperate case
  • Loading branch information
@WangTaoTheTonic
WangTaoTheTonic committed Mar 14, 2016
commit 27203d8a5d6a8a5ee8431a34d9e48aa0c6a15157
9 changes: 4 additions & 5 deletions yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -975,12 +975,11 @@ private[spark] class Client(
case e: ApplicationNotFoundException =>
logError(s"Application $appId not found.")
return (YarnApplicationState.KILLED, FinalApplicationStatus.KILLED)
case e: Exception if (e.isInstanceOf[InterruptedException]
|| e.getCause.isInstanceOf[InterruptedException]) =>
logInfo("The reporter thread is interrupted, we assume app is finished.")
return (YarnApplicationState.FINISHED, FinalApplicationStatus.SUCCEEDED)
Copy link
Contributor

@tgravescs tgravescs Mar 22, 2016

Choose a reason for hiding this comment

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

how about we change the status to be UNDEFINED.

Since we really don't know the status it seems like returning the undefined in this case make more sense. Hopefully the user would then go look more at the RM or spark job details.

case NonFatal(e) =>
if (e.isInstanceOf[InterruptedException]
|| e.getCause.isInstanceOf[InterruptedException]) {
logInfo("The reporter thread is interrupted, we assume app is finished.")
return (YarnApplicationState.FINISHED, FinalApplicationStatus.SUCCEEDED)
}
logError(s"Failed to contact YARN for application $appId.", e)
return (YarnApplicationState.FAILED, FinalApplicationStatus.FAILED)
}
Expand Down