Hitesh Shah created YARN-352:
--------------------------------
Summary: Inconsistent picture of how a container was killed when
querying RM and NM in case of preemption
Key: YARN-352
URL: https://issues.apache.org/jira/browse/YARN-352
Project: Hadoop YARN
Issue Type: Bug
Reporter: Hitesh Shah
When the RM preempts a container, it records the exit status as -100. However,
at the NM, it registers the preempted container's exit status as simply killed
by an external via SIGTERM or SIGKILL.
When the AM queries the RM and NM for the same container's status, it will get
2 different values.
When killing a container, the exit reason should likely be more defined via an
exit status code for the AM to act on in addition to providing of the
diagnostic messages that can contain more detailed information ( though
probably not programmatically interpret-able by the AM ).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
