[jira] [Updated] (MAPREDUCE-3475) JT can't renew its own tokens
[ https://issues.apache.org/jira/browse/MAPREDUCE-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated MAPREDUCE-3475: Resolution: Fixed Status: Resolved (was: Patch Available) > JT can't renew its own tokens > - > > Key: MAPREDUCE-3475 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3475 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.205.0 >Reporter: Daryn Sharp >Assignee: Daryn Sharp > Fix For: 1.0.0 > > Attachments: MAPREDUCE-3475-1.patch, MAPREDUCE-3475.patch > > > When external systems submit jobs whose tasks need to submit additional jobs > (such as oozie/pig), they include their own MR token used to submit the job. > The token's renewer may not allow the JT to renew the token. The JT log will > include very long SASL/GSSAPI exceptions when the job is submitted. It is > also dubious for the JT to renew its token because it renders the expiry as > meaningless since the JT will renew its own token until the max lifetime is > exceeded. > After speaking with Owen & Jitendra, the immediate solution is for the JT to > not attempt to renew its own tokens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MAPREDUCE-3475) JT can't renew its own tokens
[ https://issues.apache.org/jira/browse/MAPREDUCE-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated MAPREDUCE-3475: -- Target Version/s: 1.0.0, 0.22.1 (was: 1.0.0) Fix Version/s: 1.0.0 Taking Owen's comment for a +1, I have committed this patch to 1.0.0 and branch-1. Leaving the jira open with the expectation that this same fix is needed in v0.22. > JT can't renew its own tokens > - > > Key: MAPREDUCE-3475 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3475 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.205.0 >Reporter: Daryn Sharp >Assignee: Daryn Sharp > Fix For: 1.0.0 > > Attachments: MAPREDUCE-3475-1.patch, MAPREDUCE-3475.patch > > > When external systems submit jobs whose tasks need to submit additional jobs > (such as oozie/pig), they include their own MR token used to submit the job. > The token's renewer may not allow the JT to renew the token. The JT log will > include very long SASL/GSSAPI exceptions when the job is submitted. It is > also dubious for the JT to renew its token because it renders the expiry as > meaningless since the JT will renew its own token until the max lifetime is > exceeded. > After speaking with Owen & Jitendra, the immediate solution is for the JT to > not attempt to renew its own tokens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3475) JT can't renew its own tokens
[ https://issues.apache.org/jira/browse/MAPREDUCE-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated MAPREDUCE-3475: --- Attachment: MAPREDUCE-3475-1.patch A truly general solution will require touching all components. This patch fixes the issues for MR tokens by checking the token's renewer against the login user. > JT can't renew its own tokens > - > > Key: MAPREDUCE-3475 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3475 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.205.0 >Reporter: Daryn Sharp >Assignee: Daryn Sharp > Attachments: MAPREDUCE-3475-1.patch, MAPREDUCE-3475.patch > > > When external systems submit jobs whose tasks need to submit additional jobs > (such as oozie/pig), they include their own MR token used to submit the job. > The token's renewer may not allow the JT to renew the token. The JT log will > include very long SASL/GSSAPI exceptions when the job is submitted. It is > also dubious for the JT to renew its token because it renders the expiry as > meaningless since the JT will renew its own token until the max lifetime is > exceeded. > After speaking with Owen & Jitendra, the immediate solution is for the JT to > not attempt to renew its own tokens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3475) JT can't renew its own tokens
[ https://issues.apache.org/jira/browse/MAPREDUCE-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated MAPREDUCE-3475: --- Status: Patch Available (was: Open) > JT can't renew its own tokens > - > > Key: MAPREDUCE-3475 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3475 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.205.0 >Reporter: Daryn Sharp >Assignee: Daryn Sharp > Attachments: MAPREDUCE-3475.patch > > > When external systems submit jobs whose tasks need to submit additional jobs > (such as oozie/pig), they include their own MR token used to submit the job. > The token's renewer may not allow the JT to renew the token. The JT log will > include very long SASL/GSSAPI exceptions when the job is submitted. It is > also dubious for the JT to renew its token because it renders the expiry as > meaningless since the JT will renew its own token until the max lifetime is > exceeded. > After speaking with Owen & Jitendra, the immediate solution is for the JT to > not attempt to renew its own tokens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-3475) JT can't renew its own tokens
[ https://issues.apache.org/jira/browse/MAPREDUCE-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated MAPREDUCE-3475: --- Attachment: MAPREDUCE-3475.patch > JT can't renew its own tokens > - > > Key: MAPREDUCE-3475 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3475 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.205.0 >Reporter: Daryn Sharp >Assignee: Daryn Sharp > Attachments: MAPREDUCE-3475.patch > > > When external systems submit jobs whose tasks need to submit additional jobs > (such as oozie/pig), they include their own MR token used to submit the job. > The token's renewer may not allow the JT to renew the token. The JT log will > include very long SASL/GSSAPI exceptions when the job is submitted. It is > also dubious for the JT to renew its token because it renders the expiry as > meaningless since the JT will renew its own token until the max lifetime is > exceeded. > After speaking with Owen & Jitendra, the immediate solution is for the JT to > not attempt to renew its own tokens. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
