Patrick, Could you explain a bit more, why do you think that striped pool is the reason? Striped pool is where cache operations happen. So, if you see, that it consumes a lot of CPU, then it probably means, that a lot of cache operations are coming to the cluster.
You can record a JFR and see, where most time is spent. For more information refer to the following page: https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-flightrecorder-settings Denis вт, 14 мая 2019 г. в 10:43, wbyeh <[email protected]>: > We are using Ignite 2.7 as a 4-server-node session cluster but recent weeks > we found some Ignite WebSessionFilter client threads eating up CPU usage > after days of running. > The GC is running smoothly. > > How to address the root cause? > Is it a Ignite 2.x known issue with StripedExecutor? > > Can experts here point out any solutions? > > Attached file contained thread dump & 'top' usage. > > 811261.jstack > <http://apache-ignite-users.70518.x6.nabble.com/file/t645/811261.jstack> > > > Thank you! > > -Patrick > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
