RMWebService should expose a new api which gets a CapacityScheduler Configuration as an input, validates it and returns success / failure.
- causes
-
YARN-10347 Fix double locking in CapacityScheduler#reinitialize in branch-3.1
-
- Resolved
-
- is related to
-
YARN-10139 ValidateAndGetSchedulerConfiguration API fails when cluster max allocation > default 8GB
-
- Resolved
-
-
YARN-10100 [CS] Separate config validation steps from the update part
-
- Open
-