First 10 long running cache futures [total=1]

classic Classic list List threaded Threaded
4 messages Options
marble.zhong@coinflex.com marble.zhong@coinflex.com
Reply | Threaded
Open this post in threaded view
|

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
org.apache.ignite.internal.diagnostic  - >>> Future [startTime=00:16:20.109,
curTime=00:18:10.030, fut=GridNearAtomicSingleUpdateFuture [reqState=Primary
[id=06dc8f4f-b33a-45c1-8c0d-c6a62527fae1, opRes=true, expCnt=4, rcvdCnt=3,
primaryRes=false, done=false,
waitFor=[1e36906c-fae5-49a3-b67a-9eed6ada7e4e],
rcvd=[de1a8ef5-f0ca-41b1-87f5-dfe9f4517fab,
48cc4679-c256-4666-a39d-76fbd915ac02,
f0f38fba-4963-42dd-a64e-774057a61044]],
super=GridNearAtomicAbstractUpdateFuture [remapCnt=100,
topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], remapTopVer=null,
err=null, futId=1, super=GridFutureAdapter [ignoreInterrupts=false,
state=INIT, res=null, hash=316835640]]]]

thanks a lot.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ilya.kasnacheev ilya.kasnacheev
Reply | Threaded
Open this post in threaded view
|

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

Hello!

This means a cache operation takes longer to complete than usual, mostly due to locking, node network unavailability, checkpoint, etc...

Regards,
--
Ilya Kasnacheev


пн, 13 июл. 2020 г. в 09:20, [hidden email] <[hidden email]>:
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
org.apache.ignite.internal.diagnostic  - >>> Future [startTime=00:16:20.109,
curTime=00:18:10.030, fut=GridNearAtomicSingleUpdateFuture [reqState=Primary
[id=06dc8f4f-b33a-45c1-8c0d-c6a62527fae1, opRes=true, expCnt=4, rcvdCnt=3,
primaryRes=false, done=false,
waitFor=[1e36906c-fae5-49a3-b67a-9eed6ada7e4e],
rcvd=[de1a8ef5-f0ca-41b1-87f5-dfe9f4517fab,
48cc4679-c256-4666-a39d-76fbd915ac02,
f0f38fba-4963-42dd-a64e-774057a61044]],
super=GridNearAtomicAbstractUpdateFuture [remapCnt=100,
topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], remapTopVer=null,
err=null, futId=1, super=GridFutureAdapter [ignoreInterrupts=false,
state=INIT, res=null, hash=316835640]]]]

thanks a lot.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
marble.zhong@coinflex.com marble.zhong@coinflex.com
Reply | Threaded
Open this post in threaded view
|

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/
ilya.kasnacheev ilya.kasnacheev
Reply | Threaded
Open this post in threaded view
|

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, [hidden email] <[hidden email]>:
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/