ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ilya Kasnacheev <ilya.kasnach...@gmail.com>
Subject Re: Blocked system-critical thread has been detected. This can lead to cluster-wide undefined behaviour
Date Wed, 23 Jan 2019 14:35:07 GMT

As a general principle you should avoid doing any blocking operations from
event handlers, which is precisely something that you are doing.

If you replace run() with runAsync() in your service impl, it will finish
all right with two ServerNode's.

Ilya Kasnacheev

ср, 23 янв. 2019 г. в 16:34, Humphrey <hmmlopez@gmail.com>:

> Hello everyone,
> I'm getting the error below when running more than 1 ServerNode.
> The idea what we want to achive is the following:
> 1) A client node will be adding data (ALPHA) to a partitioned cache
> 2) In the cluster (server nodes) we have a Node-Singleton Service deployed,
> which has a continuous query to handle the CREATED events of the data added
> from the client on local cache (cache.setLocal(true)).
> 3) For each ALPHA event we should generate one (or more) BRAVO data and add
> them to the cache(CACHE_BRAVO), this is done by a compute task in the event
> handler.
> This seems to work fine until we start a second ServerNode. What are we
> doing wrong here? We would like to process the events generated by the
> CACHE_ALPHA with compute tasks. Eventually we would like to have another
> Service as well for handling events of CACHE_BRAVO, but we already facing
> problems handling events of the continuous query of one cache on multiple
> server nodes.
> I have a reproducer attached here.
> striped-pool-starvation.zip
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1004/striped-pool-starvation.zip>
> Humphrey
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

View raw message