hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-352) Inconsistent picture of how a container was killed when querying RM and NM in case of preemption
Date Tue, 13 May 2014 21:29:16 GMT

     [ https://issues.apache.org/jira/browse/YARN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated YARN-352:
-----------------------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: YARN-45

> 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: Sub-task
>            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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message