[
https://issues.apache.org/jira/browse/MAPREDUCE-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447486#comment-16447486
]
stefanlee commented on MAPREDUCE-7084:
--------------------------------------
[~jlowe]Thanks for your reply
{quote}Is this reproducible
{quote}
it's hard to reappear
{quote}Is the RM log filtered for just this application or the entire log?
{quote}
because the log in RM is too large, so it's filtered by applicationId, and i
did not found any exception in RM entire log.
{quote}Did the application transition out of the RUNNING state after the 10
minute expiration?
{quote}
yes,it seems the applicaiton can't unregister in 10 minutes and RM also can't
receive its heatbeat .
{quote}Is this really against Apache Hadoop 2.4.0?
{quote}
yes, our version is 2.4.0 , i don't know if this bug also exist in 2.7.0 .
> MRAppmaster still running after hadoop job -kill
> -------------------------------------------------
>
> Key: MAPREDUCE-7084
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7084
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster
> Affects Versions: 2.4.0
> Reporter: stefanlee
> Priority: Major
> Attachments: RM.log
>
>
> My scenario as follows:
> 1. I kill a application by *hadoop job -kill*.
> 2. the *FinalStatus* is *KILLED*, but its *State* is *RUNNING*
> 3. the MRAppmaster process has quit in NodeManager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
