-
Notifications
You must be signed in to change notification settings - Fork 425
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
TEZ-4543: Throw a special exception to DagClient when there is no current DAG #338
Conversation
48423ae
to
3c13443
Compare
This comment was marked as outdated.
This comment was marked as outdated.
🎊 +1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor comments, rest looks good
* Fatal exception: thrown by the AM if there is no DAG running when | ||
* when a DAG's status is queried. This is different from {@link org.apache.tez.dag.api.DAGNotRunningException} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit
two times when, once in first line & then in second
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:) fixing it
@@ -408,6 +409,8 @@ private DAGStatus getDAGStatusViaAM(@Nullable Set<StatusGetOpts> statusOptions, | |||
} catch (ApplicationNotFoundException e) { | |||
LOG.info("DAG is no longer running - application not found by YARN", e); | |||
dagCompleted = true; | |||
} catch (NoCurrentDAGException e) { | |||
return dagLost(e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the exception e
isn't used in the method dagLost
, we can remove that param., moreover I think we can explore having a info log with the exception before returning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed
thanks, fixed in ba93717 |
🎊 +1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is an AM + client-side change to make DagClient realize much faster when its asking for the status of a DAG which is not present.