Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 11 May 2017 17:55:04 +0000 (UTC)
From: "Haibo Chen (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.13018349.1478316801000.189575.1494525304407@Atlassian.JIRA>
In-Reply-To: <JIRA.13018349.1478316801000@Atlassian.JIRA>
References: <JIRA.13018349.1478316801000@Atlassian.JIRA> <JIRA.13018349.1478316801034@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (YARN-5841) Report only local collectors on node
 upon resync with RM after RM fails over
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 11 May 2017 17:55:10 -0000


     [ https://issues.apache.org/jira/browse/YARN-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Haibo Chen resolved YARN-5841.
------------------------------
    Resolution: Not A Problem

> Report only local collectors on node upon resync with RM after RM fails over
> ----------------------------------------------------------------------------
>
>                 Key: YARN-5841
>                 URL: https://issues.apache.org/jira/browse/YARN-5841
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Varun Saxena
>            Assignee: Haibo Chen
>
> As per discussion on YARN-3359, we can potentially optimize reporting of collectors to RM after RM fails over.
> Currently NM would report all the collectors known to itself in HB after resync with RM. This would mean many NMs' may pretty much report similar set of collector infos in first NM HB on reconnection. 
> This JIRA is to explore how to optimize this flow and if possible, fix it.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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