hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3469) ZKRMStateStore: Avoid setting watches that are not required
Date Tue, 14 Apr 2015 11:38:16 GMT

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

Hudson commented on YARN-3469:

FAILURE: Integrated in Hadoop-Yarn-trunk #897 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/897/])
Fix up author name to Jun Gong in CHANGES.txt for YARN-3469 (kasha: rev 5cda6fffd39fcb997b6e3cbcd0a2e2dce07153e1)
* hadoop-yarn-project/CHANGES.txt

> ZKRMStateStore: Avoid setting watches that are not required
> -----------------------------------------------------------
>                 Key: YARN-3469
>                 URL: https://issues.apache.org/jira/browse/YARN-3469
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.6.0
>            Reporter: Jun Gong
>            Assignee: Jun Gong
>            Priority: Minor
>             Fix For: 2.8.0
>         Attachments: YARN-3469.01.patch
> In ZKRMStateStore, most operations(e.g. getDataWithRetries, getDataWithRetries, getDataWithRetries)
set watches on znode. Large watches will cause problem such as [ZOOKEEPER-706: large numbers
of watches can cause session re-establishment to fail|https://issues.apache.org/jira/browse/ZOOKEEPER-706].
> Although there is a workaround that setting jute.maxbuffer to a larger value, we need
to adjust this value once there are more app and attempts stored in ZK. And those watches
are useless now. It might be better that do not set watches.

This message was sent by Atlassian JIRA

View raw message