-
Bug
-
Resolution: Done
-
Blocker
-
8.0.0.GA
-
None
-
False
-
None
-
False
-
Regression
-
-
-
-
-
-
-
-
We have a 4 nodes cluster where we deploy an application using granular cache; fail-over is introduces by stop&start of each node in sequence;
We observed that restart takes longer than usual: ~3minutes (used to be ~13sec);
Each node is configured as follows:
embed-server --server-config=standalone-ha.xml if (outcome != success) of /subsystem=jgroups:read-attribute(name=default-stack) /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) else /subsystem=jgroups:write-attribute(name=default-stack,value=tcp) /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) end-if # doubled number of credits use by MFC and UFC between 7.4.x and 8.0.x - but this value is too high for the test environment /subsystem=jgroups/stack=tcp/protocol=UFC:map-put(name=properties, key=max_credits, value=2m) /subsystem=jgroups/stack=tcp/protocol=MFC:map-put(name=properties, key=max_credits, value=2m)
The issue was, most probably, caused by a recent JGroups upgrade;
Before JGroups upgrade ~ 13sec ( wlf_20234719-144745-wildfly-service-2-server.log
):
2023-04-19 15:00:22,138 INFO [org.jboss.modules] (main) JBoss Modules version 2.0.3.Final-redhat-00001 ... 2023-04-19 15:00:35,331 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://10.0.155.165:9990/management 2023-04-19 15:00:35,331 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://10.0.155.165:9990
After JGroups upgrade ~ 3min ( wlf_20235619-115640-wildfly-service-2-server.log ):
2023-04-19 12:09:23,743 INFO [org.jboss.modules] (main) JBoss Modules version 2.1.0.Final ... 2023-04-19 12:12:18,144 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://10.0.102.196:9990/management 2023-04-19 12:12:18,145 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://10.0.102.196:9990