Re: EntryProcessor invoked twice

I think this is definitely a bug. Imagine that EP is used to maintain a counter, and the counter is incremented with every update. In this case the counter will be updated 2 times instead of 1. Alexey G., would be nice to hear your thoughts here. D. On Wed, Dec 2, 2015 at 9:08 PM, Valentin

RE: EntryProcessor invoked twice

provide more reasonable implementations and their users seem to be quite content with the performance. Cheers Andrey > From: dsetrak...@gridgain.com > Date: Thu, 3 Dec 2015 10:35:34 -0800 > Subject: Re: EntryProcessor invoked twice > To: dev@ignite.apache.org > > Point taken. &g

Re: EntryProcessor invoked twice

ementations and their users seem to be quite content > with the performance. > > Cheers > Andrey > > > From: dsetrak...@gridgain.com > > Date: Thu, 3 Dec 2015 10:35:34 -0800 > > Subject: Re: EntryProcessor invoked twice > > To: dev@ignite.apache.org > > &g

Re: EntryProcessor invoked twice

Point taken. However I still don’t get why it should be called twice in PESSIMISTIC mode. Can someone explain? D. On Thu, Dec 3, 2015 at 10:04 AM, Andrey Gura wrote: > Hi, > > Recently Alexey Goncharuk wrote in thread "EntryProcessor execution > semantics": > > For

Re: EntryProcessor invoked twice

Dmitry, Counter will not be incremented twice, because the entry is locked and EP is guaranteed to be called both times for the same old value. So there is no critical bug here in my view, but I just don't see the reason why we call it two times instead of one for one operation. -Val On Thu,

Re: EntryProcessor invoked twice

Hi, Recently Alexey Goncharuk wrote in thread "EntryProcessor execution semantics": For example, in a case of explicit optimistic > READ_COMMITTED transaction it may be called more than once because Ignite > needs to calculate a return value for the first invoke() and then it should > be called

EntryProcessor invoked twice

Igniters, I noticed that when I execute cache.invoke() in transactional cache, it's invoked twice for the same old value on the primary node. First invocation is done on prepare step [1], the second one happens on commit [2]. Is this expected behavior? Why can't we reuse already calculated new