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

Validation of joining node data consistency WRT the same data in grid

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • persistence

    Description

      Scenario

      Consider the following simple scenario (persistence is active):

      1. Start nodes A and B, activate, add (K1, V1) to cache.
      2. Stop A; update K1 to (K1, V2) (only B is aware of update). Stop B.
      3. Start A, activate, update K1 to (K1, V3).
        After that B joining the cluster will lead to ambiguity of K1 value.

      Also even having BaselineTopology tracking history of cluster nodes activations won't help here as after #3 node B's history is compatible with node A's history.

      Description

      When there is load of data updates and user turns off nodes one by one, it is important to start nodes back in the opposite order. Node turned off the last must be started first and so one.
      If it is not the case, situations like described above may happen.

      A mechanism to detect this scenarios and refuse to join nodes with potentially conflicting data is needed.

      Attachments

        Activity

          People

            Unassigned Unassigned
            sergey-chugunov Sergey Chugunov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: