Just to round up and close off, albeit a one person thread, the moral of
the story - "read the documentation" (
http://www.jgroups.org/manual/html/user-advanced.html) ... I've got
clustering working fine :-)
On Tue, Oct 11, 2016 at 1:50 PM, gambol <gambol99(a)gmail.com> wrote:
Hiya
I'm running Keycloak inside Kubernetes and attempting to get clustering
working. Multicasting is isn't available so i'm attempting to get the
gossip protocol working.
Version: 2.2.1-Final
I've changed the standalone-ha.xml
<subsystem xmlns="urn:jboss:domain:jgroups:4.0">
<channels default="ee">
<channel name="ee" stack="tcp"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP"
socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"
socket-binding="jgroups-udp-fd
"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
<stack name="tcp">
<transport type="TCP"
socket-binding="jgroups-tcp"/>
<protocol type="TCPGOSSIP">
<property name="initial_hosts">${env.GOS
SIP_ROUTER_HOST:127.0.0.1}[12001]</property>
</protocol>
<protocol type="MPING"
socket-binding="jgroups-mping"
/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"
socket-binding="jgroups-tcp-fd
"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
</stacks>
The gossip router service were using is jboss/jgroups-gossip
12:40:53,114 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000078:
Starting JGroups channel ejb
12:40:53,114 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000078:
Starting JGroups channel server
12:40:53,114 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000078:
Starting JGroups channel hibernate
12:40:53,114 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000078:
Starting JGroups channel keycloak
12:40:53,114 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000078:
Starting JGroups channel web
12:40:53,216 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000094:
Received new cluster view for channel ejb: [keycloak-4062290770-sn7jb|0]
(1) [keycloak-4062290770-sn7jb]
12:40:53,216 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000094:
Received new cluster view for channel hibernate:
[keycloak-4062290770-sn7jb|0] (1) [keycloak-4062290770-sn7jb]
12:40:53,216 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000094:
Received new cluster view for channel server: [keycloak-4062290770-sn7jb|0]
(1) [keycloak-4062290770-sn7jb]
12:40:53,217 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000094:
Received new cluster view for channel keycloak:
[keycloak-4062290770-sn7jb|0] (1) [keycloak-4062290770-sn7jb]
12:40:53,216 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000094:
Received new cluster view for channel web: [keycloak-4062290770-sn7jb|0]
(1) [keycloak-4062290770-sn7jb]
12:40:53,221 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000079:
Channel keycloak local address is keycloak-4062290770-sn7jb, physical
addresses are [10.10.69.4:7600]
12:40:53,221 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000079:
Channel server local address is keycloak-4062290770-sn7jb, physical
addresses are [10.10.69.4:7600]
12:40:53,221 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000079:
Channel hibernate local address is keycloak-4062290770-sn7jb, physical
addresses are [10.10.69.4:7600]
12:40:53,221 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000079:
Channel web local address is keycloak-4062290770-sn7jb, physical addresses
are [10.10.69.4:7600]
12:40:53,221 INFO [org.infinispan.remoting.tran
sport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000079:
Channel ejb local address is keycloak-4062290770-sn7jb, physical addresses
are [10.10.69.4:7600]
12:40:53,314 INFO [org.infinispan.factories.GlobalComponentRegistry]
(MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Mahou'
8.1.0.Final
12:40:53,314 INFO [org.infinispan.factories.GlobalComponentRegistry]
(MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou'
8.1.0.Final
12:40:53,314 INFO [org.infinispan.factories.GlobalComponentRegistry]
(MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Mahou'
8.1.0.Final
12:40:53,314 INFO [org.infinispan.factories.GlobalComponentRegistry]
(MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou'
8.1.0.Final
12:40:55,110 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 60) WFLYCLINF0002: Started users cache from keycloak
container
12:40:55,111 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 52) WFLYCLINF0002: Started realms cache from keycloak
container
12:40:55,114 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 56) WFLYCLINF0002: Started sessions cache from keycloak
container
12:40:55,113 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 54) WFLYCLINF0002: Started work cache from keycloak container
12:40:55,117 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 59) WFLYCLINF0002: Started offlineSessions cache from
keycloak container
12:40:55,117 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 58) WFLYCLINF0002: Started authorization cache from keycloak
container
12:40:55,115 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 55) WFLYCLINF0002: Started loginFailures cache from keycloak
container
12:40:58,330 INFO [org.keycloak.services] (ServerService Thread Pool --
58) KC-SERVICES0001: Loading config from standalone.xml or domain.xml
12:41:00,911 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 58) WFLYCLINF0002: Started userRevisions cache from keycloak
container
12:41:00,921 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 58) WFLYCLINF0002: Started realmRevisions cache from
keycloak container
But no matter what i seem to change ... I can't multiple pods to see the
membership ... Note, i don't even see a reference to the gossip route
itself, so i'm not entirely sure it's being used.
Are there any working examples or perhaps something obvious i'm missing?
Rohith