[
https://issues.apache.org/jira/browse/YARN-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387577#comment-15387577
]
Sunil G commented on YARN-5203:
-------------------------------
[~vvasudev], we added app priorities in 2.8. But what we are seeing here is
container priorities and its present from initial 2.x releases itself.
Thanks [~subru] and [~ellenfkh]. I understood the real issue here, and there is
no disagreement that we need to move to a cleaner jaxb object as suggested. For
new yarn-ui, we can use new object and its fine from my end. My concern was
that whether we may break some clients in coming release who were using old
api. thoughts?
> Return ResourceRequest JAXB object in ResourceManager Cluster Applications
> REST API
> -----------------------------------------------------------------------------------
>
> Key: YARN-5203
> URL: https://issues.apache.org/jira/browse/YARN-5203
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Subru Krishnan
> Assignee: Ellen Hui
> Attachments: YARN-5203.v0.patch, YARN-5203.v1.patch
>
>
> The ResourceManager Cluster Applications REST API returns {{ResourceRequest}}
> as String rather than a JAXB object. This prevents downstream tools like
> Federation Router (YARN-3659) that depend on the REST API to unmarshall the
> {{AppInfo}}. This JIRA proposes updating {{AppInfo}} to return a JAXB version
> of the {{ResourceRequest}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
