[jira] [Created] (IGNITE-17123) Fix partition counter reservation.

["Andrey Mashenkov (Jira)" <ji...@apache.org>]

Andrey Mashenkov created IGNITE-17123:
-----------------------------------------

             Summary: Fix partition counter reservation.
                 Key: IGNITE-17123
                 URL: https://issues.apache.org/jira/browse/IGNITE-17123
             Project: Ignite
          Issue Type: Bug
          Components: cache
            Reporter: Andrey Mashenkov


Transaction reserves partition counters on primary. 
On the backup side, TxEntries must be commited with counters from the reserved range.
However, a range of update counters, which were reserved on primary, is NOT validated on backup. Thus means NOOP invoke operation may cause partition counter difference on the primary and backup nodes.

1. Let's pass NOOP result of invoke operation to the backup and avoid incorrect partition counter change on backup nodes (see DhtTxPrepareFuture).
2. Update counter can be assigned to TxEntry instantly on tx commit on Remote node (for the WAL purposes) instead of allocate+iterate over 
new collection (GridDistributedTxRemoteAdapter.commitIfLocked).





--
This message was sent by Atlassian Jira
(v8.20.7#820007)