Author: anierbeck
Date: Thu Apr 11 16:01:52 2013
New Revision: 1466935
URL: http://svn.apache.org/r1466935
Log:
[KARAF-2263] - Cellar-Cloud: discover member removes member information which
isn't re-generated
Modified:
karaf/cellar/branches/cellar-2.2.x/manual/src/main/webapp/user-guide/cloud.conf
Modified:
karaf/cellar/branches/cellar-2.2.x/manual/src/main/webapp/user-guide/cloud.conf
URL:
http://svn.apache.org/viewvc/karaf/cellar/branches/cellar-2.2.x/manual/src/main/webapp/user-guide/cloud.conf?rev=1466935&r1=1466934&r2=1466935&view=diff
==============================================================================
---
karaf/cellar/branches/cellar-2.2.x/manual/src/main/webapp/user-guide/cloud.conf
(original)
+++
karaf/cellar/branches/cellar-2.2.x/manual/src/main/webapp/user-guide/cloud.conf
Thu Apr 11 16:01:52 2013
@@ -29,4 +29,9 @@ credential=<the credential/password of t
container=<the name of the bucket>
validity=<the amount of time an entry is considered valid, after that time the
entry is removed>
-After creating the file the service will check for new nodes. If new nodes are
found the Hazelcast instance configuration is updated and the instance is
restarted.
\ No newline at end of file
+After creating the file the service will check for new nodes. If new nodes are
found the Hazelcast instance configuration is updated and the instance is
restarted.
+
+h2. Configuring Cellar - Hazelcast
+
+To use the black-board approach you need to switch from the multicast join
strategy to the tcpIpJoin strategy. At this point it's safe to keep the entries
empty since the self containing node will be added during runtime.
+All other nodes will be visible the time their information is stored to the S3
bucket. (or in case of another storage in that one)
\ No newline at end of file
