Junping Du commented on YARN-313:

Thanks [~elgoiri] for rebasing the patch!

bq. Unless the patch is ready to go and the JIRA is a critical fix, we'll defer 
it to 2.6.2. Let me know if you have comments. Thanks!
Agree to the defer. I think we should target it to 2.8 as the whole feature is 
expected to be ready in that timeline. 

bq. I would appreciate ideas on why this change breaks the refreshNodes with a 
graceful period.
It is because following code to check args number is not true any more when we 
have gracefully decommission get in recently. 
+        "-refreshNodes".equals(cmd) || "-refreshResources".equals(cmd) ||
Remove "-refreshNodes".equals(cmd)" should make test pass.

> Add Admin API for supporting node resource configuration in command line
> ------------------------------------------------------------------------
>                 Key: YARN-313
>                 URL: https://issues.apache.org/jira/browse/YARN-313
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Junping Du
>            Assignee: Junping Du
>            Priority: Critical
>         Attachments: YARN-313-sample.patch, YARN-313-v1.patch, 
> YARN-313-v2.patch, YARN-313-v3.patch, YARN-313-v4.patch, YARN-313-v5.patch, 
> YARN-313-v6.patch, YARN-313-v7.patch
> We should provide some admin interface, e.g. "yarn rmadmin -refreshResources" 
> to support changes of node's resource specified in a config file.

This message was sent by Atlassian JIRA

Reply via email to