hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3581) Deprecate -directlyAccessNodeLabelStore in RMAdminCLI
Date Wed, 27 May 2015 19:46:18 GMT

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

Wangda Tan commented on YARN-3581:
----------------------------------

[~Naganarasimha], 
Thanks for update, the latest patch looks good. And I think it's better to add to 2.7.1 as
well to avoid people use it. We will not remove these options in 2.8, but we should let people
know about the risk.

Wangda

> Deprecate -directlyAccessNodeLabelStore in RMAdminCLI
> -----------------------------------------------------
>
>                 Key: YARN-3581
>                 URL: https://issues.apache.org/jira/browse/YARN-3581
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, client, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Naganarasimha G R
>         Attachments: YARN-3581.20150525-1.patch, YARN-3581.20150528-1.patch
>
>
> In 2.6.0, we added an option called "-directlyAccessNodeLabelStore" to make RM can start
with label-configured queue settings. After YARN-2918, we don't need this option any more,
admin can configure queue setting, start RM and configure node label via RMAdminCLI without
any error.
> In addition, this option is very restrictive, first it needs to run on the same node
where RM is running if admin configured to store labels in local disk.
> Second, when admin run the option when RM is running, multiple process write to a same
file can happen, this could make node label store becomes invalid.



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

Mime
View raw message