Re: [jgroups-dev] JGroups TCP Configuration clarification request

Hi Olexandr,

answers inline

On 03/02/15 16:08, Olexandr Markushyn wrote:
> Greetings,
>
> Please, could you clarify my understanding of meaning of jgroups.bind_add=
r?
>
> We have
>
> 1).Cluster consisting of two nodes (-*IP1-*, -*IP2-*).
>
> 2).Tcp configuration like
>
> =85
>           bind_addr=3D"${swp.jgroups.bind_addr:127.0.0.1}"
>           bind_port=3D"${swp.jgroups.tcp.bind_port:7800}"
>
> =85
>      <TCPPING timeout=3D"3000"
>
>
> initial_hosts=3D"${swp.jgroups.tcpping.initial_hosts:localhost[7800],loca=
lhost[7801]}"
> port_range=3D"${swp.jgroups.tcp.port_range:1}"
> num_initial_members=3D"3"/>
>
> =85
>
> 3).JVM configuration like =93-Djgroups.bind_addr=3Dsite_local
> -Dswp.jgroups.tcp.bind_port=3D<some port>=94
>
> 4).jgroups 3.3.5

Ouch ! I'm answering for 3.6.x (but IIRC this hasn't changed)

> So are next statements correct?
> 1). site_local will be used instead of
> <bind_addr=3D"${swp.jgroups.bind_addr:127.0.0.1}">

No. You'll need to start this with -Dswp.jgroups.bind_addr=3Dsite_local =

for a site local address to be used. Why did you use -Djgroups.bind_addr =

instead ?

> 2). site_local represents ranges 192.168.x.x or 10.0.x.x (according to
> https://issues.jboss.org/browse/JGRP-1204)

Yes

> 3). in case one IP address is specified as value of bind_addr that host
> is treated as =93central=94 of a cluster and all candidates having the sa=
me
> IP and the same group name will be connected into one cluster

I don't understand what you mean...

>     3.1).in such case when =93central=94 is down cluster is broken.
>
> 4). two candidates having different (range or concrete IP) value of
> bind_addr but the same group name will not be organized into one cluster


Yes


> 5).it is impossible to specify range of IP addresses as value of
> bind_addr except GLOBAL, SITE_LOCAL, etc.

Huh ?

> It means it is impossible to specify something like bind_addr=3DIP1, IP2

Yes

> 6). bind_addr contains IPs which are looked up for a cluster to connect to

No: bind_addr is the network interface that the socket(s) are binding to =

and is also used to generate the physical address used to send messages.

> 7). bind_addr contains IPs which are allowed to be connected to a cluster

No

> Best regards,
>
> Oleksandr Markushyn
>
> SoftWeb

-- =

Bela Ban, JGroups lead (http://www.jgroups.org)

---------------------------------------------------------------------------=
---
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Javagroups-development mailing list