Author: [email protected]
Date: Wed Feb 15 12:07:02 2012
New Revision: 2086
Log:
[AMDATUCASSANDRA-154] Enhanced documentation of the hector.autoDiscoverHosts
property
Modified:
trunk/amdatu-cassandra/config/src/main/resources/org.amdatu.core.cassandra.client.cfg
Modified:
trunk/amdatu-cassandra/config/src/main/resources/org.amdatu.core.cassandra.client.cfg
==============================================================================
---
trunk/amdatu-cassandra/config/src/main/resources/org.amdatu.core.cassandra.client.cfg
(original)
+++
trunk/amdatu-cassandra/config/src/main/resources/org.amdatu.core.cassandra.client.cfg
Wed Feb 15 12:07:02 2012
@@ -128,7 +128,16 @@
# addresses of all nodes in the ring, which will be added to the list of
available
# hosts the connection manager can create connections to.
# Effectively, setting this option to true will auto-expand hector.hosts to all
-# available nodes in the cluster.
+# available nodes in the cluster. However, auto discovery of hosts has some
limitations:
+# - In case the IP addresses used by the Cassandra nodes in the ring to
communicate with
+# eachother are not the same IP addresses used buy external Thrift clients
to connect
+# to these nodes (ie private vs public IPs) then the hosts might resolve to
IP
+# addresses that are not accessible by the Cassandra client.
+# - Since the auto discovery of nodes is not a background process, a Cassandra
node
+# that is added while the client is already running will not be appended to
the list
+# of auto discovered nodes. As a consequence, not all nodes will have the
same list
+# of discovered hosts and schema modifications might be send to more then
one node,
+# which may result in concurrent schema modification exceptions.
hector.autoDiscoverHosts = false
# Defines the amount of seconds to wait after initialization of the Hector
connection
_______________________________________________
Amdatu-commits mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-commits
