hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chun Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3469) ZKRMStateStore: Avoid setting watches that are not required
Date Mon, 15 Jun 2015 03:14:01 GMT

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

Chun Chen commented on YARN-3469:
---------------------------------

Just a note. I saw ZOOKEEPER-706 has been resolved recently after 5 years.

> 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.7.1
>
>         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
(v6.3.4#6332)

Mime
View raw message