[
https://issues.apache.org/jira/browse/YARN-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184087#comment-14184087
]
Steve Loughran commented on YARN-2744:
--------------------------------------
stopping the yarn services ought to be done in a finally clause;
{{ServiceOperations.stopQuietly()}} can aid this
> Under some scenario, it is possible to end up with capacity scheduler
> configuration that uses labels that no longer exist
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-2744
> URL: https://issues.apache.org/jira/browse/YARN-2744
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler
> Affects Versions: 2.5.1
> Reporter: Sumit Mohanty
> Assignee: Wangda Tan
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: YARN-2744-20141025-1.patch
>
>
> Use the following steps:
> * Ensure default in-memory storage is configured for labels
> * Define some labels and assign nodes to labels (e.g. define two labels and
> assign both labels to the host on a one host cluster)
> * Invoke refreshQueues
> * Modify capacity scheduler to create two top level queues and allow access
> to the labels from both the queues
> * Assign appropriate "label + queue" specific capacities
> * Restart resource manager
> Noticed that RM starts without any issues. The labels are not preserved
> across restart and thus the capacity-scheduler ends up using labels that are
> no longer present.
> At this point submitting an application to YARN will not succeed as there are
> no resources available with the labels.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
