hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2632) Document NM Restart feature
Date Fri, 07 Nov 2014 21:10:34 GMT

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

Jason Lowe commented on YARN-2632:
----------------------------------

Thanks for the update, Vinod.

yarn.nodemanager.address description ends in ">>>" which shows up in the rendering.

I think "ShuffleService" should be "mapreduce_shuffle" or ShuffleHandler since that's what
it's called in everyone's yarn-site.xml.

 In the auxiliary service discussion we may also want to mention that the mapreduce_shuffle
service automatically supports recovery as long as NM recovery is enabled.  Users shouldn't
have to do anything special for configuring that auxiliary service to support recovery unless
they had previously configured an ephemeral shuffle port.

> Document NM Restart feature
> ---------------------------
>
>                 Key: YARN-2632
>                 URL: https://issues.apache.org/jira/browse/YARN-2632
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>            Reporter: Junping Du
>            Assignee: Junping Du
>            Priority: Blocker
>         Attachments: NodeManagerRestart.html, YARN-2632-v2.patch, YARN-2632-v3.patch,
YARN-2632-v4.patch, YARN-2632.patch
>
>
> As a new feature to YARN, we should document this feature's behavior, configuration,
and things to pay attention.



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

Mime
View raw message