curator-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [2/3] curator git commit: doc
Date Mon, 24 Aug 2015 17:32:09 GMT


Branch: refs/heads/CURATOR-248
Commit: 2e1e92e162ef812a9d076695500f0bda8b15b6c5
Parents: 45df7ba
Author: randgalt <>
Authored: Mon Aug 24 12:30:33 2015 -0500
Committer: randgalt <>
Committed: Mon Aug 24 12:30:33 2015 -0500

 src/site/confluence/errors.confluence | 7 +++++++
 1 file changed, 7 insertions(+)
diff --git a/src/site/confluence/errors.confluence b/src/site/confluence/errors.confluence
index 28805e0..c9545ac 100644
--- a/src/site/confluence/errors.confluence
+++ b/src/site/confluence/errors.confluence
@@ -31,5 +31,12 @@ appropriate action. These are the possible state changes:
 {{UnhandledErrorListener}} is called when a background task, etc. catches an exception. In
general, Curator users shouldn't care
 about these as they are logged. However, you can listen for them if you choose.
+h2. Error Policy
+Curator has a pluggable error policy. The default policy takes the conservative approach
of treating connection states SUSPENDED and LOST the same way.
+i.e. when a recipe sees the state change to SUSPENDED it will assume that the ZooKeeper session
is lost and will clean up any watchers, nodes, etc. You can choose,
+however, a more aggressive approach by setting the error policy to only treat LOST (i.e.
true session loss) as an error state. Do this in the CuratorFrameworkFactory via:
+{{errorPolicy(new SessionErrorPolicy())}}.
 h2. Recipes
 In general, the recipes attempt to deal with errors and connection issues. See the doc for
each recipe for details on how it deals with errors.

View raw message