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 <[email protected] >: > Can someone please advise? > > On Wed 26 Feb, 2020, 12:23 AM Prasad Bhalerao < > [email protected] 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 >>> >>
