-
1. Re: Getting cache to join an existing distributed cluster
mircea.markus Oct 11, 2010 4:56 AM (in response to gupabhi)Hi,
Now I wanted to use an embedded programatic cache that would become part of the same cluster. I cannot seem to get the embedded cache to become part of the demo cluster.
I suggest you add following VM params when you start the cluster:
-Djgroups.bind_addr = IP - the ip of the network card where you want you cluster to bind to. If both nodes are running on the same machine, just add -Djgroups.bind_addr=127.0.0.1. -Djava.net.preferIPv4Stack=true just to make sure that specified IP addresses are in IPv4 format.
-
2. Re: Getting cache to join an existing distributed cluster
mircea.markus Oct 11, 2010 5:01 AM (in response to gupabhi)1 of 1 people found this helpfulre:discovery. it is possible to avoid using UDP entirely. You'll have to amend the jgroups configuration file to do that. though. FILE_PING is such a discovery protocol that relies on a shared network disk. ALternatively you can also use TCPPING or a gossip router. Refer to jgroup's documentation for more on this.
-
3. Re: Getting cache to join an existing distributed cluster
gupabhi Oct 19, 2010 8:05 PM (in response to mircea.markus)Thanks Mircea. I've got my cluster to use TCP for communication and TCPPing for discovery.
Two more related questions to communication -
* I could not find any articles that discuss the pros and cons of the various discovery protocols in the context of infinispan. Points to ponder about might be related to redundancy, efficient, flexible, dynamic, single-point-of-failure, etc.
* I see that infinispan ships with a hotrod server script and I've read how the hotrod server could be made part of the cluster. My question is, how does infinispan internally talk across the cluster? For example, in case of a sync-replicated cluster, does it send the entries across all nodes using hotrod or some other protocol, or can this be configured? I could not find an obvious way to configure it from this page (http://docs.jboss.org/infinispan/4.1/apidocs/config.html)
Thanks in advance.
-Abhi
-
4. Re: Getting cache to join an existing distributed cluster
mircea.markus Oct 20, 2010 6:40 AM (in response to gupabhi)* I could not find any articles that discuss the pros and cons of the various discovery protocols in the context of infinispan. Points to ponder about might be related to redundancy, efficient, flexible, dynamic, single-point-of-failure, etc.
I can't think of any discovery aspects particular to Infinispan.
I see that infinispan ships with a hotrod server script and I've read how the hotrod server could be made part of the cluster. My question is, how does infinispan internally talk across the cluster? For example, in case of a sync-replicated cluster, does it send the entries across all nodes using hotrod or some other protocol, or can this be configured? I could not find an obvious way to configure it from this page (http://docs.jboss.org/infinispan/4.1/apidocs/config.html)
Hotrod is only used for clients to connect to an infinispan cluster. For communicating between its members (e.g. replicating state) infinispan uses jgroups.