Re: Killing a node under load stalls the grid with ignite 1.7

Hi, It should not be in CacheStore implementation, but i if you does not want re-write logic, do it asynchronously. On Thu, Nov 3, 2016 at 6:35 PM, bintisepaha wrote: > the problem is when I am in write behind for order, how do I access the > trade > object. its only

Re: Killing a node under load stalls the grid with ignite 1.7

the problem is when I am in write behind for order, how do I access the trade object. its only present in the cache. at that time I need access trade cache and that is causing issues. -- View this message in context:

Re: Killing a node under load stalls the grid with ignite 1.7

Hi, I mean, If you need create Order entry before Trade, you can to do it in CacheStore implementation, but do not use IgniteCache for this. Just write inserts for both tables. Why this way did not matched? On Mon, Oct 31, 2016 at 4:55 PM, bintisepaha wrote: > Hi

Re: Killing a node under load stalls the grid with ignite 1.7

Hi, You need to write into "write behind handler" to database only (you can fill several table, if it needed, for example "Order" than "Trade"). Cache which has "read through" on table "Trade" will always read value from database, until cache entry does not exist. On Thu, Oct 27, 2016 at 6:03

Re: Killing a node under load stalls the grid with ignite 1.7

yes I think you are write. Is there any setting that we can use in write behind that will not lock the entries? the use case is we have is like this Parent table - Order (Order Cache) Child Table - Trade (Trade Cache) We only have write behind on Order Cache and when writing that we write order

Re: Killing a node under load stalls the grid with ignite 1.7

Hi, Incorrect implementation of CacheStore is the most probable reason, because stored entry is locked. You need to avoid lock one entry in othe. Necessary re-write the code and re-check, I think, the issue will resolved. On Tue, Oct 25, 2016 at 1:05 AM, bintisepaha

Re: Killing a node under load stalls the grid with ignite 1.7

Hi, actually we use a lot of caches from cache store writeAll(). For confirming if that is the cause of the grid stall, we would have to completely change our design. Can someone confirm that this is the cause for grid to stall? referencing cache.get from a cache store and then killing or

Re: Killing a node under load stalls the grid with ignite 1.7

Hi, Yes, please attach new dumps (without putting in cache into cache store). That reduce search of reason. On Fri, Oct 21, 2016 at 3:54 PM, bintisepaha wrote: > This was done to optimize our writes to the DB. on every save, we do not > want > to delete and insert

Re: Killing a node under load stalls the grid with ignite 1.7

This was done to optimize our writes to the DB. on every save, we do not want to delete and insert records, so we do a digest comparison. Do you think this causes an issue? How does cache store handle transactions or locks? when a node dies, if a flusher thread is doing write-behind how does that

Re: Killing a node under load stalls the grid with ignite 1.7

Hi, I have just saw: at org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1214) at com.tudor.datagridI.server.writebehind.BasePersistentService.replaceDigest(BasePersistentService.java:302) at

Re: Killing a node under load stalls the grid with ignite 1.7

Hi, I don't have a simple working example. But under even some load its a very reproducible problem. We had the same issue with ignite 1.5.0-final as well. Never used 1.6 as much, and now have the same issue with 1.7.0. If you are able to reproduce on your end , it will be really helpful. Where

Re: Killing a node under load stalls the grid with ignite 1.7

Hi Binti, I can not reproduce this issue. Could you please provide cache configuration? On Thu, Oct 13, 2016 at 6:48 PM, vdpyatkov wrote: > Hi Binti, > > Hi, > This is look like a lock GridCacheWriteBehindStore and > GridCachePartitionExchangeManager. > > Could you give

Re: Killing a node under load stalls the grid with ignite 1.7

Hi Binti, Hi, This is look like a lock GridCacheWriteBehindStore and GridCachePartitionExchangeManager. Could you give work an example of this? If not I try to reproduce it tomorrow -- View this message in context:

Re: Killing a node under load stalls the grid with ignite 1.7

Hi could someone please look at this and respond? Thanks, Binti -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Killing-a-node-under-load-stalls-the-grid-with-ignite-1-7-tp8130p8158.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Killing a node under load stalls the grid with ignite 1.7

Hi, we are using ignite 1.7 and under some load when caches are being updated and write behind is moving along if we just kill a node, the entire grid stalls. attaching thread dumps when the partitioned caches were in full_sync mode and also when all were in full_async mode. It looks like