Eric Payne updated YARN-4225:
    Attachment: YARN-4225.002.patch

Attaching {{YARN-4225.002.patch}}, which implements {{getPreemptionDisabled()}} 
to return a {{Boolean}}, and {{QueueCLI#printQueueInfo}} will check for 
non-null before printing out queue status. Patch applies cleanly to trunk, 
branch-2, and branch-2.8.
In General, what is the Hadoop policy when a newer client talks to an older 
server and the protobuf output is different than expected. Should we expose 
some form of the has method, or should we overload the get method as I 
described here?

I would appreciate any additional feedback from the community in general (Vinod 
Kumar Vavilapalli, do you have any thoughts?)
[~vinodkv], did you have a chance to think about this? [~jlowe], do you have 
any additional thoughts?

> Add preemption status to yarn queue -status for capacity scheduler
> ------------------------------------------------------------------
>                 Key: YARN-4225
>                 URL: https://issues.apache.org/jira/browse/YARN-4225
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler, yarn
>    Affects Versions: 2.7.1
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>            Priority: Minor
>         Attachments: YARN-4225.001.patch, YARN-4225.002.patch

This message was sent by Atlassian JIRA

Reply via email to