Re: [jgroups-dev] Need information about Jgroup communication in jgroups 2.6.5

On 2/16/11 12:56 PM, Ashish Giri wrote:
> Hi Bela,
>
> We are trying with 2.6.13 version for now. Hoping our issue will get resolve with that.
>
> About API we have used and that are changed:
> Our requirement was having cross core/subnet communication[whole subnet as a single jgroups cluster] using jgroups. As it was not supported in 2.6.5 version.


I don't understand: communication across a subnet has nothing to do with 
JGroups, this is a network configuration issue...

What do you understand by 'cross subnet communication' ?


> Thinking of using RELAY protocol. Few questions:
> 1. Not able to find enough example and tcp.xml configuration details for cross subnet communication?


This is work-in-progress. I'm working on RELAY as we speak... I'll have 
a talk about RELAT at JBossWorld 2011.


> 2. Read that application can't transfer own header? Is it correct. Because we have defined some headers of our own.


Yes, this was the idea originally. However, I've recently changed this: 
all headers with IDs >= 200 *will* be copied. This is for example 
necessary to enable RpcDispatchers to run correctly between clusters 
bridged with RELAY.


> 3. In this two subnet will be in different jgroup cluster and bridge cluster will join this two subnet. Is this understanding correct?


Yes. 2 local clusters bridged with RELAY will appear as if they were 1 
virtual cluster.

> 4. How to define tcp.xml configuration of other subnet? Means all host information of other subnet or both subnet.


If you don't want to list all members of both local clusters, you have 
the following options for discovery across TCP:
- TCPGOSSIP and GossipRouter
- S3_PING (EC2)
- FILE_PING, e.g. over a shared NFS mount, accessible by both clusters
- JDBC_PING (new): shared DB, accessible by both clusters


-- 
Bela Ban
Lead JGroups / Clustering Team
JBoss

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Javagroups-development mailing list