hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ying Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5614) NMClient APIs do not need to take NodeId
Date Fri, 02 Sep 2016 08:26:20 GMT

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

Ying Zhang commented on YARN-5614:

Sounds reasonable.

> NMClient APIs do not need to take NodeId
> ----------------------------------------
>                 Key: YARN-5614
>                 URL: https://issues.apache.org/jira/browse/YARN-5614
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Jian He
> Currently, all the NMClient APIs, e.g. startContainer, stopContainer, getContainerStatus
force caller to pass in the NodeId as wells as the ContainerId.  Hence, caller has to maintain
both NodeId and ContainerId mapping on its own, which becomes a bit inconvenient sometimes.
> In fact, NMClient internally already cached the NodeId for the ContainerId, so the NodeId
in the API could be avoided.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message