[
https://issues.apache.org/jira/browse/YARN-10732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330865#comment-17330865
]
Peter Bacsko commented on YARN-10732:
-------------------------------------
[~gandras] the old queue state comes from a {{CSQueueStore}} which can be
mocked or a mock CSQueue can be added with a DRAINING state. The new queue can
be set to RUNNING in the config. I think this scanario is testable.
It's also a bit regrettable that {{validateQueueHierarchy()}} is completely
untested, at least there is no unit test for it in
{{TestCapacitySchedulerConfigValidator}}. I think it could be a good idea to
provide tests for it, if not in this JIRA, then maybe in a follow-up.
> Disallow restarting a queue while it is in DRAINING state on CS
> reinitialization
> --------------------------------------------------------------------------------
>
> Key: YARN-10732
> URL: https://issues.apache.org/jira/browse/YARN-10732
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn
> Reporter: Andras Gyori
> Assignee: Andras Gyori
> Priority: Major
> Attachments: YARN-10732.001.patch
>
>
> CSConfigValidator#validateQueueHierarchy does not check a state where the old
> queue is in DRAINING state but the new queue state is RUNNING. User should
> wait until a queue is fully stopped.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
