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 22:08:00 GMT

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

Chandni Singh commented on YARN-7440:

When a ServiceRecord doesn't exist for multiple containers belonging to the same component,
then it is possible that a container is assigned to a different component instance when the
AM recovers. 
Discussed this issue with [~jianhe] and [~billie.rinaldi] offline. Swapping containers to
different component instances will cause naming conflicts inside the container process.  Currently
we don't get the component name from the _Container_, so in order to implement this correctly
we need to wait for https://issues.apache.org/jira/browse/YARN-6594.

> 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

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

View raw message