[
https://issues.apache.org/jira/browse/HADOOP-16034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738130#comment-16738130
]
Steve Loughran commented on HADOOP-16034:
-----------------------------------------
Been thinking about a test 4 this.
Obvious one: configure client with an invalid IPv4 addr (192.255.255.256) and
expect it to fail as curator is set up, which will move from service init to
the actual first operation
> 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
> Attachments: HADOOP-16034-001.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
