curator-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From randg...@apache.org
Subject [05/14] curator git commit: minor typo
Date Tue, 01 Sep 2015 02:48:22 GMT
minor typo


Project: http://git-wip-us.apache.org/repos/asf/curator/repo
Commit: http://git-wip-us.apache.org/repos/asf/curator/commit/bc57786c
Tree: http://git-wip-us.apache.org/repos/asf/curator/tree/bc57786c
Diff: http://git-wip-us.apache.org/repos/asf/curator/diff/bc57786c

Branch: refs/heads/CURATOR-247
Commit: bc57786c9c55f06f8918e0e2255277bfb2fbbecb
Parents: b8240a1
Author: randgalt <randgalt@apache.org>
Authored: Mon Aug 24 11:11:16 2015 -0500
Committer: randgalt <randgalt@apache.org>
Committed: Mon Aug 24 11:11:16 2015 -0500

----------------------------------------------------------------------
 src/site/confluence/errors.confluence | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/curator/blob/bc57786c/src/site/confluence/errors.confluence
----------------------------------------------------------------------
diff --git a/src/site/confluence/errors.confluence b/src/site/confluence/errors.confluence
index 0111cf4..a744128 100644
--- a/src/site/confluence/errors.confluence
+++ b/src/site/confluence/errors.confluence
@@ -26,7 +26,7 @@ appropriate action. These are the possible state changes:
 |READ_ONLY|The connection has gone into read\-only mode. This can only happen if you pass
true for CuratorFrameworkFactory.Builder.canBeReadOnly(). See the ZooKeeper doc regarding
read only connections: [[http://wiki.apache.org/hadoop/ZooKeeper/GSoCReadOnlyMode]]. The connection
will remain in read only mode until another state change is sent.|
 |SUSPENDED|There has been a loss of connection. Leaders, locks, etc. should suspend until
the connection is re\-established.|
 |RECONNECTED|A suspended or lost connection has been re\-established.|
-|LOST|Curator will set the LOST state when it believes that the ZooKeeper session has expired.
ZooKeeper connections have a session. When the session expires, clients must take appropriate
action. In Curator, this is complicated by the fact that Curator internally manages the ZooKeeper
connection. Curator will set the LOST state when any of the following occurs: a) ZooKeeper
returns a Watcher.Event.KeeperState.Expired or KeeperException.Code.SESSIONEXPIRED; b) Curator
closes the internally managed ZooKeeper instance; c) The session timeout elapses during a
network partition. It is possible to get a RECONNECTED state after this but you should still
consider any locks, etc. as dirty/unstable. *NOTE* The meaning of LOST has changed since Curator
3.0.0. Prior to 3.0.0 LOST only meant that the retry policy had expired.|
+|LOST|Curator will set the LOST state when it believes that the ZooKeeper session has expired.
ZooKeeper connections have a session. When the session expires, clients must take appropriate
action. In Curator, this is complicated by the fact that Curator internally manages the ZooKeeper
connection. Curator will set the LOST state when any of the following occurs: a) ZooKeeper
returns a Watcher.Event.KeeperState.Expired or KeeperException.Code.SESSIONEXPIRED; b) Curator
closes the internally managed ZooKeeper instance; c) The session timeout elapses during a
network partition. It is possible to get a RECONNECTED state after this but you should still
consider any locks, etc. as dirty/unstable. *NOTE*: The meaning of LOST has changed since
Curator 3.0.0. Prior to 3.0.0 LOST only meant that the retry policy had expired.|
 
 {{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.


Mime
View raw message