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

Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/08/15 20:32:21 UTC

[jira] [Updated] (MAPREDUCE-5332) Support token-preserving restart of history server

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

Jason Lowe updated MAPREDUCE-5332:
----------------------------------

    Attachment: MAPREDUCE-5332.patch

Patch that adds token persistence in a similar manner to how it is done for the RM.  One major difference is that an error in the token persistence layer is not fatal as it is for the RM.  My thinking is it would be better for the history server to stay up than just fall over for any filesystem hiccup.  It's easy to change this if people think that the history server should crash when this occurs.
                
> Support token-preserving restart of history server
> --------------------------------------------------
>
>                 Key: MAPREDUCE-5332
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5332
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: jobhistoryserver
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: MAPREDUCE-5332.patch
>
>
> To better support rolling upgrades through a cluster, the history server needs the ability to restart without losing track of delegation tokens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira