Hi Ilya, didn't get what are you trying to say. The problem I am facing is, my transaction is failing giving TransactionOptimisticException. I do not have a reproducer for this project and this does not happen frequently. Transaction is failing during prepare phase. I had to open a debug port on all grid nodes to do remote debugging in order to debug this issue. What I observed is transaction fails because check in GridCacheMapEntry.checkSerializableReadVersion fails as the nodeOrder in GridCacheVersion in serialized version is different from the actual noderOrder in GridCacheVersion of respective node. This method returns false on 2 nodes out 4 nodes and this is happening for Replicated cache.
This is the reason I asked What is nodeOrder in GridCacheVersion and why it is important while checking read entries in Transaction context? I tried to debug nodeOrder in ignite code but could not understand it. Inside transaction I am reading and modifying Replicated as well as Partitioned cache. What I observed is this fails for Replicated cache. As workaround, I have moved the code which reads Replicated cache out of transaction block. Is it allowed to read and modify both replicated and Partitioned cache i.e. use both Replicated and Partition? Complete exception can be found here <https://gist.github.com/61979329224e23dbaef2f63976a87a14.git>. Thanks, Prasad On Thu, Feb 27, 2020 at 1:00 AM Ilya Kasnacheev <ilya.kasnach...@gmail.com> wrote: > Hello! > > I don't think this is userlist discussion, this logging is not aimed at > end-user and you are not supposed to act on it. > > Do you have any context for us, such as reproducer project or complete > logs? > > Regards, > -- > Ilya Kasnacheev > > > ср, 26 февр. 2020 г. в 19:13, Prasad Bhalerao < > prasadbhalerao1...@gmail.com>: > >> Can someone please advise? >> >> On Wed 26 Feb, 2020, 12:23 AM Prasad Bhalerao < >> prasadbhalerao1...@gmail.com wrote: >> >>> Hi, >>> >>>> Ignite Version: 2.6 >>>> No of nodes: 4 >>>> >>>> I am getting following exception while committing transaction. >>>> >>>> Although I just reading the value from this cache inside transaction >>>> and I am sure that the cache and "cache entry" read is not being modified >>>> out this transaction on any other node. >>>> >>>> So I debugged the code and found out that it fails in following code on >>>> 2 nodes out of 4 nodes. >>>> >>>> GridDhtTxPrepareFuture#checkReadConflict - >>>> GridCacheEntryEx#checkSerializableReadVersion >>>> >>>> GridCacheVersion version failing for equals check are given below for 2 >>>> different caches. I can see that it failing because of change in nodeOrder >>>> of cache. >>>> >>>> 1) Can some please explain the significance of the nodeOrder w.r.t Grid >>>> and cache? When does it change? >>>> 2) How to solve this problem? >>>> >>>> Cache : Addons (Node 2) >>>> serReadVer of entry read inside Transaction: GridCacheVersion >>>> [topVer=194120123, order=4, nodeOrder=2] >>>> version on node3: GridCacheVersion [topVer=194120123, order=4, >>>> nodeOrder=1] >>>> >>>> Cache : Subscription (Node 3) >>>> serReadVer of entry read inside Transaction: GridCacheVersion >>>> [topVer=194120123, order=1, nodeOrder=2] >>>> version on node2: GridCacheVersion [topVer=194120123, order=1, >>>> nodeOrder=10] >>>> >>>> >>>> *EXCEPTION:* >>>> >>>> Caused by: >>>> org.apache.ignite.internal.transactions.IgniteTxOptimisticCheckedException: >>>> Failed to prepare transaction, read/write conflict >>>> >>> >>> >>>> >>>> Thanks, >>>> Prasad >>>> >>>
