You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/11/04 01:30:32 UTC
[jira] [Updated] (YARN-4226) Make capacity scheduler queue's
preemption status REST API consistent with GUI
[ https://issues.apache.org/jira/browse/YARN-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated YARN-4226:
------------------------------------------
Target Version/s: 2.7.3 (was: 3.0.0, 2.8.0, 2.7.2)
Moving out all non-critical / non-blocker issues that didn't make it out of 2.7.2 into 2.7.3.
> Make capacity scheduler queue's preemption status REST API consistent with GUI
> ------------------------------------------------------------------------------
>
> Key: YARN-4226
> URL: https://issues.apache.org/jira/browse/YARN-4226
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler, yarn
> Affects Versions: 2.7.1
> Reporter: Eric Payne
> Assignee: Eric Payne
> Priority: Minor
>
> In the capacity scheduler GUI, the preemption status has the following form:
> {code}
> Preemption: disabled
> {code}
> However, the REST API shows the following for the same status:
> {code}
> preemptionDisabled":true
> {code}
> The latter is confusing and should be consistent with the format in the GUI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)