Hi Maxim,
I think I got it working now. I need to change the config a bit.
1. turn on mulicast and use this hazelcast config:
https://docs.hazelcast.org/docs/latest/manual/html-single/index.html#discovering-members-by-tcp
<network>
<join>
<multicast enabled="false">
</multicast>
<tcp-ip enabled="true">
<member>server1.example.com</member>
<member>server2.example.com</member>
</tcp-ip>
</join>
Greetings Peter
PS: and not a day to early... user perform "load-tests" by now....
Am 15.03.20 um 08:21 schrieb Maxim Solodovnik:
Hello Peter,
sorry for the late reply
I'm using this config for my tests:
https://github.com/apache/openmeetings/blob/master/openmeetings-web/src/main/webapp/WEB-INF/classes/hazelcast.xml
line 61: make instance-name UNIQUE (I'm using server-1, server-2 etc.)
line 64: enable multicast
line 69 uncomment, set-up ports interfaces
This config for your server nodes
Your clients will use UI
On Fri, 13 Mar 2020 at 20:26, Peter Dähn <[email protected]> wrote:
Hi Maxim,
do I need to do something like that
(https://docs.hazelcast.org/docs/3.0/manual/html/ch12s02.html#IPv6)
<hazelcast>
...
<network>
<port auto-increment="true">5701</port>
<join>
<multicast enabled="false">
<multicast-group>FF02:0:0:0:0:0:0:1</multicast-group>
<multicast-port>54327</multicast-port>
</multicast>
<tcp-ip enabled="true">
<member>[fe80::223:6cff:fe93:7c7e]:5701</member>
<interface>192.168.1.0-7</interface>
<interface>192.168.1.*</interface>
<interface>fe80:0:0:0:45c5:47ee:fe15:493a</interface>
</tcp-ip>
</join>
<interfaces enabled="true">
<interface>10.3.16.*</interface>
<interface>10.3.10.4-18</interface>
<interface>fe80:0:0:0:45c5:47ee:fe15:*</interface>
<interface>fe80::223:6cff:fe93:0-5555</interface>
</interfaces>
...
</network>
to enable IPv6 support in addition? Clients usually have both addresses but
some of them just IPv4 or IPv6 only.
Greetings Peter
