Re: First 10 long running cache futures [total=1]

Hello! The printed cache future contains some of this information, but it's hard to decipher. In this case, you are waiting for a node 1e36906c-fae5-49a3-b67a-9eed6ada7e4e. It will make sense to check its thread dump. Regards, -- Ilya Kasnacheev вт, 14 июл. 2020 г. в 05:59,

Re: First 10 long running cache futures [total=1]

thanks, are there any hints that can find/locate the operations that impact the server? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: First 10 long running cache futures [total=1]

et an exception on below, it impacts system no responses, any > suggestions how to identify the case? > > 12:18:10,035 [grid-timeout-worker-#39] WARN > org.apache.ignite.internal.diagnostic - First 10 long running cache > futures > [total=1] > 12:18:1

First 10 long running cache futures [total=1]

Hi Guru, we met an exception on below, it impacts system no responses, any suggestions how to identify the case? 12:18:10,035 [grid-timeout-worker-#39] WARN org.apache.ignite.internal.diagnostic - First 10 long running cache futures [total=1] 12:18:10,035 [grid-timeout-worker-#39] WARN