[
https://issues.apache.org/jira/browse/YARN-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396123#comment-15396123
]
Junping Du commented on YARN-5434:
----------------------------------
Thanks [~rkanter] for working out a patch here. The 002 patch looks good in
overall. A minor comments, I think we would have a non-blocking call for server
side tracking and a blocking call for client side tracking (unless not
specified timeout value which is -1 by default). Isn't it? If so, better to
mention it (blocking/non-blocking behavior) in rmadmin CLI help messages?
> Add -client|server argument for graceful decom
> ----------------------------------------------
>
> Key: YARN-5434
> URL: https://issues.apache.org/jira/browse/YARN-5434
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: graceful
> Affects Versions: 2.8.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Blocker
> Attachments: YARN-5343.001.patch, YARN-5343.002.patch
>
>
> We should add {{-client|server}} argument to allow the user to specify if
> they want to use the client-side graceful decom tracking, or the server-side
> tracking (YARN-4676).
> Even though the server-side tracking won't go into 2.8, we should add the
> arguments to 2.8 for compatibility between 2.8 and 2.9, when it's added. In
> 2.8, using {{-server}} would just throw an Exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
