Hello, I have recently encountered this "long-running cache future" message while doing stress tests on Ignite (we run it embedded inside an application server). I put CPU pressure on two out of four nodes using stress-ng, that rendered the two nodes irresponsive for the duration of the test, and then one of the other two "healthy" nodes started logging the "long running future" message.
In my opinion, it could be related to a cache operation that cannot complete due to another node(nodes?) that do not respond in time. I hope that helps a little. On Tue, Jul 30, 2019 at 3:52 PM Denis Magda <[email protected]> wrote: > Igniters, > > Does this remind you any long-running transaction, starvation or deadlock? > It's not obvious from the attached files what caused the issue. Mahesh > please share all the logs from all the nodes and apps for analysis. > > > - > Denis > > > On Sun, Jul 28, 2019 at 8:50 PM Mahesh Renduchintala < > [email protected]> wrote: > >> Hi, >> >> >> >> After a while, an ignite node becomes unresponsive printing >> >> >> >>Found long-running cache future >> >> >> Please check the attached log. >> >> >> What does "Found long-running cache future" mean? >> >> please throw some light. >> >> >> regards >> >> mahesh >> >> >>
