You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/01/08 14:17:00 UTC

[jira] [Updated] (HADOOP-16034) Hadoop/Yarn registry to create Curator binding on demand

     [ https://issues.apache.org/jira/browse/HADOOP-16034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HADOOP-16034:
------------------------------------
    Summary: Hadoop/Yarn registry to create Curator binding on demand  (was: Yarn registry to create Curator binding on demand)

> Hadoop/Yarn registry to create Curator binding on demand
> --------------------------------------------------------
>
>                 Key: HADOOP-16034
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16034
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: registry
>    Affects Versions: 3.1.1
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>
> If enough slider worker nodes are created, and then each create a Registry client, then ZK can overload even when they aren't making calls of the registry. Why so? Because curator gets started up on serviceStart(), even when not used.
> Proposed fix: make it on-demand on use of a ZK read/write operation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org