Re: Blocked system-critical thread has been detected - After upgrade to 2.8.1

[Manu <ma...@hotmail.com>]

Hi Alex, thanks so much.

We are reduced topology to picture below (1 server node and 3 clients).

- 1 Ignite server node: IMDB with persistence enabled
- 3 Ignite client nodes: for SQL query, messaging (topic, queue) and
countdown latches.

All pluggable elements (TOPIC listener and QUEUE listener) are online.

This topology works perfectly with 2.7.6. But with 2.8.1 not... 

Also we are detected that failure (blocked thread) occurs when pluggable
modules are online (green lines and blocks) and we make only 1 request (not
by heavy load).

<http://apache-ignite-users.70518.x6.nabble.com/file/t547/arch_i.png> 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Blocked system-critical thread has been detected - After upgrade to 2.8.1

[Manu <ma...@hotmail.com>]

Hi Alex

We can't share GC logs as they contains sensitive data. We have solve it by
creating a new data cluster with persistence enabled and moving data from
problematic cluster to new one.

As far as we can see, it seems that the problem is in the checkpoint
process, for some unknown reason (maybe it has to do with the migration from
2.7.6 to 2.8.1 and the new changes in persistence management) the checkpoint
thread is blocked.

Anyway, we will be attentive to this topic.

Thank you very much, greetings!




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Blocked system-critical thread has been detected - After upgrade to 2.8.1

[akorensh <al...@gmail.com>]

Manu,
  Can you set up the lightest load/simplest topology possible, send the
Ignite logs from 
  all nodes(server and clients), including the GC logs, and we will take a
look.
 
https://apacheignite.readme.io/docs/jvm-and-system-tuning#detailed-garbage-collection-stats
Thanks, Alex



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/