hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6533) Race condition in writing service record to registry in yarn native services
Date Wed, 10 May 2017 20:33:04 GMT

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

Jian He commented on YARN-6533:

yeah, sounds good to me, we can leave it unencoded. Else the code will make readers wondering
why in one place it's encoded, in another it's not

> Race condition in writing service record to registry in yarn native services
> ----------------------------------------------------------------------------
>                 Key: YARN-6533
>                 URL: https://issues.apache.org/jira/browse/YARN-6533
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>         Attachments: YARN-6533-yarn-native-services.001.patch, YARN-6533-yarn-native-services.002.patch
> The ServiceRecord is written twice, once when the container is initially registered and
again in the Docker provider once the IP has been obtained for the container. These occur
asynchronously, so the more important record (the one with the IP) can be overwritten by the
initial record. Only one record needs to be written, so we can stop writing the initial record
when the Docker provider is being used.

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