hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-396) Rationalize AllocateResponse in RM scheduler API
Date Wed, 19 Mar 2014 02:17:48 GMT

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

ASF GitHub Bot commented on YARN-396:

Github user srowen commented on the pull request:

    @tgravescs FWIW I think something like this is the case, yes. The change happened in https://issues.apache.org/jira/browse/YARN-396
which occurred for the first(?) YARN TLP release with Hadoop 2.1. And CDH 4.4 was the first
release I see that picked up this change. I assume it was useful/necessary to float this 'alpha'
API ahead.
    I also would have thought it's possible the `yarn` profile works with this release, but
I do not know. Just making sure that has been tried?
    Otherwise yeah it looks like a question of supporting another intermediate flavor of YARN
here since it did change in breaking ways several times between 0.23.x and 2.2

> Rationalize AllocateResponse in RM scheduler API
> ------------------------------------------------
>                 Key: YARN-396
>                 URL: https://issues.apache.org/jira/browse/YARN-396
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>            Assignee: Zhijie Shen
>              Labels: incompatible
>             Fix For: 2.1.0-beta
>         Attachments: YARN-396_1.patch, YARN-396_2.patch, YARN-396_3.patch, YARN-396_4.patch,
> AllocateResponse contains an AMResponse and cluster node count. AMResponse that more
data. Unless there is a good reason for this object structure, there should be either AMResponse
or AllocateResponse.

This message was sent by Atlassian JIRA

View raw message