hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chandni Singh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7440) Optimization to AM recovery when the service record doesn't exist for a container
Date Wed, 08 Nov 2017 20:26:00 GMT

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

Chandni Singh commented on YARN-7440:
-------------------------------------

Seems like the test is failing because the previous container for the service master during
_recovery_ has same {{allocationRequestId}} as one of the component containers. Either the
{{allocationRequestId}} for the service master container should be different or we can check
during recovery that if the container number is 1, then we just release it.

> Optimization to AM recovery when the service record doesn't exist for a container
> ---------------------------------------------------------------------------------
>
>                 Key: YARN-7440
>                 URL: https://issues.apache.org/jira/browse/YARN-7440
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Chandni Singh
>            Assignee: Chandni Singh
>             Fix For: yarn-native-services
>
>         Attachments: YARN-7440.001.patch, YARN-7440.002.patch
>
>
> When AM recovers, if the service record doesn’t exist for a container sent from RM,
it can re-query the container status from NM, today it will release the container



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message