[jira] [Updated] (MAPREDUCE-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-3940: - Fix Version/s: 2.0.1-alpha ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Fix For: 0.23.3, 2.0.1-alpha Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MAPREDUCE-3940-20120709.txt, MAPREDUCE-3940-20120710.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Status: Open (was: Patch Available) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MAPREDUCE-3940-20120709.txt, MAPREDUCE-3940-20120710.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Status: Patch Available (was: Open) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MAPREDUCE-3940-20120709.txt, MAPREDUCE-3940-20120710.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Attachment: MAPREDUCE-3940-20120710.txt Good catch Sid. This should fix it. ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MAPREDUCE-3940-20120709.txt, MAPREDUCE-3940-20120710.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Resolution: Fixed Fix Version/s: 0.23.3 Target Version/s: (was: 0.23.3) Release Note: ContainerTokens now have an expiry interval so that stale tokens cannot be used for launching containers. Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed this to trunk, branch-2 and branch-0.23. Thanks for the bug fixes and the reviews, Sid! ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Fix For: 0.23.3 Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MAPREDUCE-3940-20120709.txt, MAPREDUCE-3940-20120710.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Status: Open (was: Patch Available) Thanks for the update, Sid. The fix to move token-expirty to only for startContainer looks good, Thanks. Will upload a merged patch now. ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MAPREDUCE-3940-20120709.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Attachment: MAPREDUCE-3940-20120709.txt Patch upmerged to trunk. Also fixed MAPREDUCE-4295 for FifoScheduler. ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MAPREDUCE-3940-20120709.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Status: Patch Available (was: Open) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MAPREDUCE-3940-20120709.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3940: -- Status: Open (was: Patch Available) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3940: -- Status: Patch Available (was: Open) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3940: -- Attachment: MR3940.txt Upmerged to apply to trunk. ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MR3940.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3940: -- Fix Version/s: (was: 0.23.2) Target Version/s: 0.23.3 Status: Open (was: Patch Available) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3940: -- Attachment: MR3940.txt Expiry checked only for startContainer calls. Updated the unit test. ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated MAPREDUCE-3940: -- Status: Patch Available (was: Open) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt, MR3940.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Attachment: MAPREDUCE-3940-20120425.txt bq. The MR AM will end up seing some harmless exceptions when invoking stopContainer Ths issue of using ContainerTokens with stopContainer() and getContainerStatus() is known, but I did miss the MR AM getting exceptions. We will need to fix circumventing the verification logic of ContainerTokens for the stopContainer() and getContainerStatus() APIs, will open a separate ticket. Short term, we can get this into trunk and merge it into 23 branches after the followup ticket is fixed. Updating the patch to be applicable against later trunk. ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Fix For: 0.23.2 Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Status: Patch Available (was: Open) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Fix For: 0.23.2 Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt, MAPREDUCE-3940-20120425.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Status: Open (was: Patch Available) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Fix For: 0.23.2 Attachments: MAPREDUCE-3940-20120308.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Attachment: MAPREDUCE-3940-20120416.txt Patch that applies over latest trunk. ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Fix For: 0.23.2 Attachments: MAPREDUCE-3940-20120308.txt, MAPREDUCE-3940-20120416.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Status: Patch Available (was: Open) ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Fix For: 0.23.2 Attachments: MAPREDUCE-3940-20120308.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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-3940) ContainerTokens should have an expiry interval
[ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated MAPREDUCE-3940: --- Attachment: MAPREDUCE-3940-20120308.txt Attaching patch that adds expiry time to container-token-ids and makes NM reject containers with expired tokens. Added a unit test to exactly validate the above. ContainerTokens should have an expiry interval -- Key: MAPREDUCE-3940 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3940 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: mrv2, security Affects Versions: 0.23.0 Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Fix For: 0.23.2 Attachments: MAPREDUCE-3940-20120308.txt - RM should generate the expiry time for a container - A ContainerToken should have its expire time encoded - NMs should reject containers with expired tokens. - Expiry interval for a ContainerToken is same as the expiry interval for a container. -- 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
