hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6680) Avoid locking overhead for NO_LABEL lookups
Date Mon, 19 Jun 2017 15:46:00 GMT

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

Naganarasimha G R commented on YARN-6680:

Thanks [~jlowe], agree with you on the multi-thread scenario/issue, that was the reason i
was trying to mention that when ever write happens we need to update a new resource object
instead of updating the existing one which will avoid the issue which you mentioned.
Ok as i get other additional +1, i will commit this shortly !

> Avoid locking overhead for NO_LABEL lookups
> -------------------------------------------
>                 Key: YARN-6680
>                 URL: https://issues.apache.org/jira/browse/YARN-6680
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.8.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>         Attachments: YARN-6680.patch
> Labels are managed via a hash that is protected with a read lock.  The lock acquire and
release are each just as expensive as the hash lookup itself - resulting in a 3X slowdown.

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