hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler
Date Wed, 02 Dec 2015 23:30:11 GMT

    [ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036864#comment-15036864
] 

Wangda Tan commented on YARN-4225:
----------------------------------

Thanks [~eepayne],
bq. The use case is a newer client is querying an older server...
I'm wondering if this is a valid use case: IMHO, rolling upgrade should be always server-first.
If we plan support newer client talks to older server, we may experience many issues AND we
need to add this to Hadoop's code compatibility policy.

> 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, YARN-4225.003.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message