hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3940) ContainerTokens should have an expiry interval
Date Wed, 18 Apr 2012 23:50:40 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257097#comment-13257097

Siddharth Seth commented on MAPREDUCE-3940:

One issue with the patch...
The MR AM will end up seing some harmless exceptions when invoking stopContainer (similarly
for getContainerStatus invocations) for any container which runs beyond the configured limit
(default 10 minutes). These containers will however eventually end up being killed via the
RM - once the AM releases them.
> 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


View raw message