hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Templeton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6761) Fix build for YARN-3926 branch
Date Mon, 10 Jul 2017 08:27:00 GMT

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

Daniel Templeton commented on YARN-6761:

Thanks for getting the patch in, [~sunilg].  Sorry I didn't get a chance to review it before
the commit.  Your patch did exactly what I would have done. :)

I have a question about the way the {{ResourceInformation}} information objects are handled
in this patch and in general.  Why do we need local copies of them?  Shouldn't there only
be one master source of truth for resource information, and shouldn't everyone just refer
to that master source of truth?  I assume that's where you're going with YARN-6789.

> Fix build for YARN-3926 branch
> ------------------------------
>                 Key: YARN-6761
>                 URL: https://issues.apache.org/jira/browse/YARN-6761
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Varun Vasudev
>            Assignee: Varun Vasudev
>             Fix For: YARN-3926
>         Attachments: YARN-6761-YARN-3926.001.patch
> After rebasing to trunk, due to the addition of YARN-6679, compilation of the YARN-3926
branch is broken.

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