Re: [jgroups-users] removing unknown address from cluster? JGRP000032

--===============1787834897262832079==
Content-Type: multipart/alternative; boundary="000000000000b5e6af05c32a7406"

--000000000000b5e6af05c32a7406
Content-Type: text/plain; charset="UTF-8"

On Tue, May 25, 2021 at 10:30 AM Questions/problems related to using
JGroups via javagroups-users <[email protected]> wrote:

> Hi Bobby
> apologies for the delay!
>

No problem -- thanks for looking.


>
> You cannot have the old cluster's initial_hosts be 128,129,130 and the
> new one has the overlapping range 130,131.
>

That's the problem. The customer has lots of nodes, clusters that grow and
shrink, and they're going to reuse the same IP addresses eventually.


>
> The old cluster will try to contact 130 (e.g. trying to merge), thereby
> send its information to 130.
>

Right, and what they want is some way to fully remove a node from a
cluster. I.e. the cluster stops trying to contact that address.


>
> What is it you're trying to achieve?
>

Simply to take a node out of a cluster when it's not needed, then later
reuse the address of that node with a different cluster. If I change the
cluster names (same port though) then I still get constant warnings, like:
JGRP000012: discarded message from different cluster <old> (our cluster is
<new>). Sender was <some addr>

We can suggest that they restart the cluster after removing a node, but I
don't know if that will work for them. I'll also try using different ports
for different clusters and see how that works for them. Given the size of
the company in question, I can see that it might be hard to coordinate that
and eventually they'll get back in the same situation where a previously
used address is being used again with the same port it used the last time.

Thanks,
Bobby

--000000000000b5e6af05c32a7406
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, May 25, 2021 at 10:30 AM Question=
s/problems related to using JGroups via javagroups-users &lt;<a href=3D"mai=
lto:[email protected]">[email protected]=
rge.net</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">Hi Bobby<br>
apologies for the delay!<br></blockquote><div><br></div><div>No problem -- =
thanks for looking.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">
<br>
You cannot have the old cluster&#39;s initial_hosts be 128,129,130 and the =
<br>
new one has the overlapping range 130,131.<br></blockquote><div><br></div><=
div>That&#39;s the problem. The customer has lots of nodes, clusters that g=
row and shrink, and they&#39;re going to reuse the same IP addresses eventu=
ally.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
<br>
The old cluster will try to contact 130 (e.g. trying to merge), thereby <br=
>
send its information to 130.<br></blockquote><div><br></div><div>Right, and=
 what they want is some way to fully remove a node from a cluster. I.e. the=
 cluster stops trying to contact that address.</div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><br>
What is it you&#39;re trying to achieve?<br></blockquote><div><br></div><di=
v>Simply to take a node out of a cluster when it&#39;s not needed, then lat=
er reuse the address of that node with a different cluster. If I change the=
 cluster names (same port though) then I still get constant warnings, like:=
</div><div>JGRP000012: discarded message from different cluster &lt;old&gt;=
 (our cluster is &lt;new&gt;). Sender was &lt;some addr&gt;<br></div><div><=
br></div><div>We can suggest that they restart the cluster after removing a=
 node, but I don&#39;t know if that will work for them. I&#39;ll also try u=
sing different ports for different clusters and see how that works for them=
. Given the size of the company in question, I can see that it might be har=
d to coordinate that and eventually they&#39;ll get back in the same situat=
ion where a previously used address is being used again with the same port =
it used the last time.</div><div><br></div><div>Thanks,</div><div>Bobby</di=
v><div><br></div></div></div>

--000000000000b5e6af05c32a7406--


--===============1787834897262832079==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============1787834897262832079==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
javagroups-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/javagroups-users

--===============1787834897262832079==--