You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Virag Kothari (JIRA)" <ji...@apache.org> on 2013/01/02 19:52:13 UTC

[jira] [Commented] (OOZIE-1148) Set the renewer correctly for JT/RM delegation tokens

    [ https://issues.apache.org/jira/browse/OOZIE-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542285#comment-13542285 ] 

Virag Kothari commented on OOZIE-1148:
--------------------------------------

looks good..+1
                
> Set the renewer correctly for JT/RM delegation tokens
> -----------------------------------------------------
>
>                 Key: OOZIE-1148
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1148
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 3.3.0
>            Reporter: Rohini Palaniswamy
>            Assignee: Rohini Palaniswamy
>             Fix For: trunk, 3.3.1
>
>         Attachments: OOZIE-1148-branch3.3.patch, OOZIE-1148-trunk.patch
>
>
> HadoopAccessorService sets the renewer as "oozie mr token" for the delegation tokens instead of the JT or RM service principal name. Because of this long running jobs fail if the token lifetime is not set to 7 days (some value > 2 days) by JT. JT (Hadoop 1.0.2) did not have support for renewing and cancelling tokens to itself and so it did not matter what the renewer was set to. But that support is being added in RM in Hadoop 0.23/2.0.0 in YARN-50 as it would lead to RM going OOM as it runs with lot less memory than JT.  

--
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