Recipes such as TreeCache are susceptible to herding on reconnections

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.