Re: Deadlock detection usage

Andrey, Can you tell me what transaction is being blocked? If it is the transaction in deadlock, then I think it should not matter, as it is blocked anyway. D. On Sun, May 22, 2016 at 2:11 PM, Andrey Gura wrote: > Dmitry, > > Do you think that we should configure deadlock

Re: Eviction Events with offheap values

I don't think that evicition from offheap to swap should fire EVT_CACHE_OBJECT_EXPIRED event because it will indistinguishable from normal eviction event. On Fri, May 20, 2016 at 3:06 AM, Dmitriy Setrakyan wrote: > Andrey, I think there should be an eviction event fired,

Re: Deadlock detection usage

Dmitry, Do you think that we should configure deadlock detection using cache configuration? User should have possibility to have control over this process because it blocks transaction until detection completion. You are right. Deadlock detection starts after transaction timeout and lists

Re: [VOTE] Apache Ignite 1.6.0 RC1

I just want to give some explanation about the two “-1” non-binding votes we have received form the community. The Apache voting process does not imply bug-free releases. Apache release needs to be clean from licensing standpoint and needs to be easily buildable. Of course, if there are critical

[GitHub] ignite pull request: IGNITE-2538 RDD.isEmpty method should be over...

GitHub user f7753 opened a pull request: https://github.com/apache/ignite/pull/741 IGNITE-2538 RDD.isEmpty method should be overriden in IgniteRDD to use IgniteCache API Currently calling `IgniteRDD.isEmpty` ends up in execution of 1024 Spark jobs, which is not fast. We should