Karthik Kambatla commented on YARN-3469:

When working on YARN-2716, I was wondering about the same. I think not setting 
watches makes sense. I ll let [~jianhe] also comment before committing this. 

> Do not set watch for most cases in ZKRMStateStore
> -------------------------------------------------
>                 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
>         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

Reply via email to