You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2018/02/12 00:23:00 UTC

[jira] [Updated] (CURATOR-441) Recipes such as TreeCache are susceptible to herding on reconnections

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

Jordan Zimmerman updated CURATOR-441:
-------------------------------------
    Fix Version/s:     (was: 4.0.1)
                   4.0.2

> Recipes such as TreeCache are susceptible to herding on reconnections
> ---------------------------------------------------------------------
>
>                 Key: CURATOR-441
>                 URL: https://issues.apache.org/jira/browse/CURATOR-441
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Framework, Recipes
>    Affects Versions: 4.0.0
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> Many of Curator's recipes (TreeCache, etc.) have to refresh their state when a connection problem is repaired. In larger systems, this could cause a thundering herd as all these clients press the ZK ensemble. It would be nice to introduce an optional Jitter mechanism into the Framework connection management so that reconnections aren't immediately reported to the recipes, but are instead delayed slightly with some randomness.



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