Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-5302

Empty LOST partition may be used as OWNING after resetting lost partitions

    XMLWordPrintableJSON

    Details

      Description

      Notes

      Test testPartitionLossAndRecover reproducing the issue can be found in ignite-5267 branch with PDS functionality.

      Steps to reproduce

      1. Four nodes are started, some key is added to partitioned cache
      2. Primary and backup nodes for the key are stopped, key's partition is declared LOST on remaining nodes
      3. Primary and backup nodes are started again, cache's lost partitions are reset
      4. Key is requested from cache

      Expected behavior

      Correct value is returned from primary for this partition

      Actual behavior

      Request for value is sent to node where partition is empty (not to primary node), null is returned

      Latest findings

      1. The main problem with the scenario is that request for key gets mapped not only to P/B nodes with real value but also to the node where that partition existed only in LOST state after P/B shutdown on step #2
      2. It was found that on step #3 after primary and backup are joined partition counter is increased for empty partition in LOST state which looks wrong

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                sergey-chugunov Sergey Chugunov
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: