YARN-11833. Do not validate queue hierarchy when failing over. #7775
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of PR
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.
How was this patch tested?
unit test