CacheEntryProcessor causes cluster node to stop

classic Classic list List threaded Threaded
4 messages Options
ihalilaltun ihalilaltun
Reply | Threaded
Open this post in threaded view
|

CacheEntryProcessor causes cluster node to stop

Hi Igniters,

Although class was deployed in SHARED or CONTINUOUS mode node got exception
and halted itself.

log added;
ignite.zip
<http://apache-ignite-users.70518.x6.nabble.com/file/t2515/ignite.zip>  


*Ignite version*: 2.7.5
*Cluster size*: 16
*Client size*: 22
*Cluster OS version*: Centos 7
*Cluster Kernel version*: 4.4.185-1.el7.elrepo.x86_64
*Java version* :
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)



-----
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
Vladimir Pligin Vladimir Pligin
Reply | Threaded
Open this post in threaded view
|

Re: CacheEntryProcessor causes cluster node to stop

Hi,

It seems that the root cause of the issue happens on node with
id=fb70df1c-0311-48b4-bb33-88cdf85438ce.
That node becomes unresponsive. Could you please share logs from that node,
it could help?



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

Re: CacheEntryProcessor causes cluster node to stop

Hi Vladimir,

here is logs from other node
ignite-3.zip
<http://apache-ignite-users.70518.x6.nabble.com/file/t2515/ignite-3.zip>  



-----
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
ilya.kasnacheev ilya.kasnacheev
Reply | Threaded
Open this post in threaded view
|

Re: CacheEntryProcessor causes cluster node to stop

Hello!

I can see that you had server nodes fail on activation and then there are "the tree may be corrupted" errors. This points to damaged persistence files on one or more nodes, probably due to prior running out of disk space or some kind of internal erorr.

Did it resolve in the end?

Regards,
--
Ilya Kasnacheev


ср, 17 июл. 2019 г. в 17:09, ihalilaltun <[hidden email]>:
Hi Vladimir,

here is logs from other node
ignite-3.zip
<http://apache-ignite-users.70518.x6.nabble.com/file/t2515/ignite-3.zip



-----
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/