[
https://issues.apache.org/jira/browse/YARN-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Payne updated YARN-2932:
-----------------------------
Attachment: YARN-2932.v8.txt
Thanks, [~leftnoteasy], for your reviews and your help working through this
jira.
{quote}
I feel we'd better to make config and web UI consistent, the difference between
config and web UI a little confusing. If it is not easy to modify config, I
suggest to make CapacitySchedulerPage shows "preemption disabled" and also
logging in LeafQueue.
{quote}
I'm afraid I couldn't make it all "isPreemptable," so I made everything reflect
the state of "disable_preemption". It's actually not too bad. I'll upload a
screenshot.
> Add entry for "preemptable" status to scheduler web UI and queue
> initialize/refresh logging
> -------------------------------------------------------------------------------------------
>
> Key: YARN-2932
> URL: https://issues.apache.org/jira/browse/YARN-2932
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.7.0
> Reporter: Eric Payne
> Assignee: Eric Payne
> Attachments: YARN-2932.v1.txt, YARN-2932.v2.txt, YARN-2932.v3.txt,
> YARN-2932.v4.txt, YARN-2932.v5.txt, YARN-2932.v6.txt, YARN-2932.v7.txt,
> YARN-2932.v8.txt
>
>
> YARN-2056 enables the ability to turn preemption on or off on a per-queue
> level. This JIRA will provide the preemption status for each queue in the
> {{HOST:8088/cluster/scheduler}} UI and in the RM log during startup/queue
> refresh.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
