Hi,
Yes, for complex transaction this workaround will not work. So you need
either wait for fix or avoid using EntryProcessor for now.
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Wrapping executeEntryProcessorTransaction() method in affinity run will
help if the whole data is collocated on same node. But In my case data is
distributed across cluster and I want to update whole data in single
distributed transaction.
If I collocate data on single node then cluster will
Hi Prasad,
This issue could not be completed in 2.5 as it's done in a low priority. As
a workaround, you can wrap your executeEntryProcessorTransaction() method
into affinity run [1], and no additional value transferring will happen.
[1]
https://issues.apache.org/jira/browse/IGNITE-3471
Can we please have a fix for this issue in ignite 2.5 version?
Reason:
I am trying to test the distributed transaction support using following
piece of code. While debugging the code I observed that code executes on
client node first and after
