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

Posted to yarn-dev@hadoop.apache.org by "Daryn Sharp (JIRA)" <ji...@apache.org> on 2013/01/07 21:14:13 UTC

[jira] [Created] (YARN-320) RM should always be able to renew its own tokens

Daryn Sharp created YARN-320:
--------------------------------

             Summary: RM should always be able to renew its own tokens
                 Key: YARN-320
                 URL: https://issues.apache.org/jira/browse/YARN-320
             Project: Hadoop YARN
          Issue Type: Bug
          Components: resourcemanager
    Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6
            Reporter: Daryn Sharp
            Assignee: Daryn Sharp
            Priority: Blocker


YARN-280 introduced fast-fail for job submissions with bad tokens.  Unfortunately, other stack components like oozie and customers are acquiring RM tokens with a hardcoded dummy renewer value.  These jobs would fail after 24 hours because the RM token couldn't be renewed, but fast-fail is failing them immediately.  The RM should always be able to renew its own tokens submitted with a job.  The renewer field may continue to specify an external user who can renew.

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