Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-5021

Nodes that finish the rebalance later can see outdated values

    XMLWordPrintable

Details

    Description

      Copied from ISPN-4444

      If the CH_UPDATE command is delayed on the old owner, the new owners might update the key without the old owner knowing, and a locality check on the old owner won't help.

      I remember one thing that struck me when reading the Raft algorithm was that they install configuration changes symmetrically, in 3 phases. We might need to do the same for our rebalance:
      1. T0: read_ch=old, write_ch=old
      2. start a rebalance
      3. T1: read_ch=old, write_ch=old+new
      4. new owners have all the data
      5. T2: read_ch=new, write_ch=old+new
      6. remove old cache entries and ignore further writes
      7. T3: read_ch=new, write_ch=new

      Attachments

        Issue Links

          Activity

            People

              rvansa1@redhat.com Radim Vansa
              dberinde@redhat.com Dan Berindei
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: