hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1354) Recover applications upon nodemanager restart
Date Thu, 01 May 2014 21:50:20 GMT

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

Jason Lowe updated YARN-1354:

    Attachment: YARN-1354-v2-and-YARN-1987-and-YARN-1362.patch

Updating the patch to address the DBException handling that was brought up in the MAPREDUCE-5652
review and applies here. Note that this now depends upon YARN-1987 as that provides the utility
wrapper for the leveldb iterator to translate raw RuntimeException to the more helpful DBException
so we can act accordingly when errors occur.

This patch also addresses the issue where apps were being cleaned up on shutdown.  This leverages
YARN-1362 so we can distinguish a decommission shutdown, and it will avoid cleaning up applications
if the state store can recover and we are not being decommissioned.  The other notable change
in the patch is renaming LevelDB to Leveldb for consistency with the existing LeveldbTimelineStore
naming convention.

This latest patch includes the necessary pieces of YARN-1987 and YARN-1362 so it can compile
and Jenkins can comment.

> Recover applications upon nodemanager restart
> ---------------------------------------------
>                 Key: YARN-1354
>                 URL: https://issues.apache.org/jira/browse/YARN-1354
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.3.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: YARN-1354-v1.patch, YARN-1354-v2-and-YARN-1987-and-YARN-1362.patch
> The set of active applications in the nodemanager context need to be recovered for work-preserving
nodemanager restart

This message was sent by Atlassian JIRA

View raw message