You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Li Lu (JIRA)" <ji...@apache.org> on 2016/09/19 23:51:20 UTC

[jira] [Updated] (YARN-3359) Recover collector list in RM failed over

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

Li Lu updated YARN-3359:
------------------------
    Attachment: YARN-3359-YARN-5638.patch

Posting a patch based on the solution of YARN-5638. With all app level collectors properly stamped, we can easily rebuild collector status in a resync by sending all known collector info from NMs. In this patch I'm not addressing collector life-cycle/persistency issues on the NM side. This is because addressing those problems becomes something with much different scopes, so let's address them in a separate JIRA. 

> Recover collector list in RM failed over
> ----------------------------------------
>
>                 Key: YARN-3359
>                 URL: https://issues.apache.org/jira/browse/YARN-3359
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Junping Du
>            Assignee: Li Lu
>              Labels: YARN-5355
>         Attachments: YARN-3359-YARN-5638.patch
>
>
> Per discussion in YARN-3039, split the recover work from RMStateStore in a separated JIRA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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