[
https://issues.apache.org/jira/browse/YARN-11833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028892#comment-18028892
]
ASF GitHub Bot commented on YARN-11833:
---------------------------------------
github-actions[bot] commented on PR #7775:
URL: https://github.com/apache/hadoop/pull/7775#issuecomment-3387856246
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Do not validate queue hierarchy when failing over
> -------------------------------------------------
>
> Key: YARN-11833
> URL: https://issues.apache.org/jira/browse/YARN-11833
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
> Reporter: liu bin
> Priority: Major
> Labels: pull-request-available
>
> Now if we use file configuration store, when failing over, if RM1 stopped and
> removed a queue that RM2 has in memory, failing over to RM2 will throw
> exception that queue cannot be deleted because the queue is not in stopped
> state.
> Only using mutable configuration provider can skip validate queue hierarchy,
> I think file based configuration provider should also skip validate queue
> hierarchy when failing over.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
