hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlo Curino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4957) Add getNewReservation in ApplicationClientProtocol
Date Tue, 17 May 2016 00:35:13 GMT

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

Carlo Curino commented on YARN-4957:

The number of failures is a bit large (though you account for them in your comments). I kicked
another run to see whether in the last 2-3 weeks things improved. If not, we can still commit
this, but we should open JIRAs to fix the timing and non-det issues we see in tests.

In parallel, I will go over the patch and do a review.

> Add getNewReservation in ApplicationClientProtocol
> --------------------------------------------------
>                 Key: YARN-4957
>                 URL: https://issues.apache.org/jira/browse/YARN-4957
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: applications, client, resourcemanager
>    Affects Versions: 2.8.0
>            Reporter: Subru Krishnan
>            Assignee: Sean Po
>              Labels: api-breaking
>         Attachments: YARN-4957.v0.patch, YARN-4957.v1.patch, YARN-4957.v2.patch, YARN-4957.v3.patch,
YARN-4957.v4.patch, YARN-4957.v5.1.patch, YARN-4957.v5.patch
> Currently submitReservation returns a ReservationId if sucessful. This JIRA propose adding
a getNewReservation in ApplicationClientProtocol for the following reasons:
>   * Prevent zombie reservations in the face of client and/or network failures post submitReservation
>   * Align reservation submission with application submission

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message