Hi,
GridCacheTtlManager.expire is called from different places and may lead to
cluster hanging.
It is impossible to understand from user code was the operation successful
or not when such NPE was thrown.
As this method is called (from gateway.leave() method) after operation has
been finished, so,
Thank you for the information! What are the worst consequences if I hit that
bug? Entries not being evicted?
Is my tx committed if the error is striking on commit or do I need to redo the
work that was done in the tx?
On 12. Apr 2018, at 14:30, Andrey Mashenkov
mailto:andrey.mashen...@gmail.com
Hi Dome,
It is known issue and there is a ticket for this [1] you can track.
It is hard to be reproduced due to a race.
Seems, GridCacheUtils.unwindEvicts() should check if context has been
started.
[1] https://issues.apache.org/jira/browse/IGNITE-7972
On Thu, Apr 12, 2018 at 2:39 PM, dkarach
Hi Dome,
Could you please attach full logs?
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hey all,
I'm using Apache Ignite .NET ver. 2.4.0#20180305-sha1:aa342270, running
multiple caches.
One of the caches holds entries which expire after a while.
At some point of operation I observed that two of my transactions raised
exceptions when being commited by me.
Both transactions were used
