hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1407) RM Web UI and REST APIs should uniformly use YarnApplicationState
Date Wed, 20 Nov 2013 01:42:18 GMT

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

Vinod Kumar Vavilapalli commented on YARN-1407:
-----------------------------------------------

Sandy, YARN-936 existed before. Is that a duplicate?

> RM Web UI and REST APIs should uniformly use YarnApplicationState
> -----------------------------------------------------------------
>
>                 Key: YARN-1407
>                 URL: https://issues.apache.org/jira/browse/YARN-1407
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>             Fix For: 2.2.1
>
>         Attachments: YARN-1407-1.patch, YARN-1407-2.patch, YARN-1407.patch
>
>
> RMAppState isn't a public facing enum like YarnApplicationState, so we shouldn't return
values or list filters that come from it. However, some Blocks and AppInfo are still using
RMAppState.
> It is not 100% clear to me whether or not fixing this would be a backwards-incompatible
change.  The change would only reduce the set of possible strings that the API returns, so
I think not.  We have also been changing the contents of RMAppState since 2.2.0, e.g. in YARN-891.
It would still be good to fix this ASAP (i.e. for 2.2.1).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message