Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-17845 Make Ignite Consistent Again
  3. IGNITE-17851

TX cache update counter must deny already closed gaps re-closing

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • Docs Required, Release Notes Required

    Description

      Currently PartitionUpdateCounterTrackingImpl#update() just returns false when closing already closed gaps.
      The result is ignored on non-rollback calls at IgniteTxHandler#applyPartitionsUpdatesCounters().
      Such behaviour allows to reuse the same counter and this may lead to the hidden inconsistency.

      I've checked that PartitionUpdateCounterTrackingImpl#update() never returns false on non-rollback call, using the Check, but we must guarantee this.

      PartitionUpdateCounterTrackingImpl#update() method should be refactored to provide only-once closing guarantee or IgniteTxHandler#applyPartitionsUpdatesCounters() shoud check the update result for every the call (including non-rollback).

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              av Anton Vinogradov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: