hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3327) if NMClientAsync stopContainer failed because of IOException, there's no chance to stopContainer again
Date Tue, 14 Jul 2015 15:50:04 GMT

    [ https://issues.apache.org/jira/browse/YARN-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626528#comment-14626528
] 

sandflee commented on YARN-3327:
--------------------------------

There is no logs any more, it's a long time and I just fix it by removing the statemachine
in NMClientAsyncImpl.java

> if NMClientAsync stopContainer failed because of IOException,  there's no chance to stopContainer
again
> -------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3327
>                 URL: https://issues.apache.org/jira/browse/YARN-3327
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: api, client
>    Affects Versions: 2.6.0
>            Reporter: sandflee
>
> In AM, I use NMClientAsync to control containers, when I use stopContainer to kill container
,IOException happens, then If I stopContainer again, nothing happens, because container Managed
by NMClientAsync came to FAILED state.
> In my opinion, IOException just means temporary error,it shouldn't came to FAILED state
especially when NM Restart is enabled。



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message