[ https://issues.jboss.org/browse/JGRP-2396?page=com.atlassian.jira.plugin.... ] Rob van der Boom edited comment on JGRP-2396 at 11/8/19 8:31 AM: ----------------------------------------------------------------- True many components involved. I will deliver more details next week, heap dump etc. Its more tracing down what it can and can not be, ofcourse i am not sure, only things i no so far: - there are no know keycloak related issues so far and it looks like relating to infinispan cache replication between the nodes. The issue increases/ show up only when having many cached sessions (>300.000) but it is NOT related to activity since it keeps increasing with same amount even at night when almost no traffic on the site. - Its is only the TQ bundler taken up more and more cpu not other tasks (unless heap grows towards max. but since we doubled heap GC doesnt grow above 1% cpu when tq bundler is already into the 30% and quickly after higher. Network data transfer (also when almost no trafic on site is growing as fast as the cpu to levels we can not explain since). - zero errors occure anywhere that can explain issues. So will try to hand over more details, thanks in advance was (Author: robvanderboom): True many components involved. I will deliver more details next week, heap dump etc. Its more tracing down what it can and can not be, ofcourse i am not sure, only things i no so far: - there are no know keycloak related issues so far and it looks like relating to infinispan cache replication between the nodes. The issue increases/ show up only when having many cached sessions (>300.000) but it is NOT related to activity since it keeps increasing with same amount even at night when almost no traffic on the site. - Its is only the TQ bundler taken up more and more cpu not other tasks (unless heap grows towards max. but since we doubled heap GC doesnt grow above 1% cpu when tq bundler is already into the 30% and quickly after higher. Network data transfer (also when almost no trafic on site is growing as fast as the cpu to levels we can not explain since). - zero errors occure anywhere that can explain issues. So will try to hand over more details, -- This message was sent by Atlassian Jira (v7.13.8#713008)