Hi,
1/ it's where cluster group can help: you can target the deployment of
some resources to only some subset of nodes in the same cluster group.
2/ the cluster:bundle-start command allows you to target a specific
cluster group, whereas when using bundle:start, Cellar will broadcast
the cluster event to all members of the cluster groups of the local
node. In future Cellar version, you will be able to disable the local
broadcasting: it means that bundle:start won't have effect on the
cluster, and you will have to use cluster:bundle-start.
3/ It depends of the network configuration in etc/hazelcast.xml. By
default, Cellar tries to discover the nodes using multicast/unicast. If
it's not allowed on your network, you can switch to tcp-ip discovery
(static IP address definition).
Regards
JB
On 01/09/2014 08:54 AM, simafengyun1984 wrote:
Hi JB,
I used karaf cellar 2.2.2 to construct my karaf cluster.
I tried to construct a cellar cluster in my local. I had 3 nodes in the
cluster. 3 kinds of bundles ,as below
* 1. third-party bundles(ex: spring-dm bundle) deployed in the node1
2. my customized camel component bundles deployed in the node2
3. my application bundles deployed in the node3*
when the 3 node joined in the same group, it seems all the bundles in one
node will be copy to other nodes and each of the bundles will have 3
instances in the 3 nodes.
in this case, the third-party bundles and custmized camel component bundles
are fine. but for my application bundle which is used to listening to the
JMS topic and process jms message. Apparently each JMS message will be
process in 3 times.
* Question1: Do you know any solution of keepping only one instance for a
bundle in cluster in the same time?*
*Question2: I run command start bundleID in one node. and the bundle
will be started in other nodes. *So what's the difference between command
start and cluster:bundle-start?*
I used cellar to build 2 nodes cluster.
*
*Question3: I have 2 nodes, one in IP 192.168.1.50, the other in IP
192.169.0.50. But they can't see each other and can't be connected to the
same group. Apparently the 2 IP are not in the same net segment. does it
caused by the IP which are not in the same net segment.*
--
View this message in context:
http://karaf.922171.n3.nabble.com/Please-help-to-fix-karaf-cluster-issue-tp4030950.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
