You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Benjamin Teke (Jira)" <ji...@apache.org> on 2026/10/07 09:07:00 UTC
[jira] [Created] (YARN-12019) Capacity Scheduler UI: validate staged changes on the server
Benjamin Teke created YARN-12019:
------------------------------------
Summary: Capacity Scheduler UI: validate staged changes on the server
Key: YARN-12019
URL: https://issues.apache.org/jira/browse/YARN-12019
Project: Hadoop YARN
Issue Type: Sub-task
Components: capacity scheduler
Reporter: Benjamin Teke
Assignee: Benjamin Teke
Remove the client-side validation rules from the Capacity Scheduler UI.
Staged changes are sent (debounced) to validate/v2; issues are shown on the queue and field named by queuePath and propertyKey; inherited and derived values are labeled with their source from ?explain=true. Apply sends If-Match on every write, with the ETag the previous write returned, and offers reload-and-compare on 412. After a write whose outcome is unknown or that finds a concurrent change, nothing more is written and the queues that may still be stopped are named; a failed restart after the change committed is reported as such.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org