Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Fri, 20 Oct 2017 15:39:00 +0000 (UTC)
From: "Sergey Chugunov (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.13111019.1508513882000.18923.1508513940100@Atlassian.JIRA>
In-Reply-To: <JIRA.13111019.1508513882000@Atlassian.JIRA>
References: <JIRA.13111019.1508513882000@Atlassian.JIRA> <JIRA.13111019.1508513882445@jira-lw-us.apache.org>
Subject: [jira] [Created] (IGNITE-6695) Validation of joining node data
 consistency WRT the same data in grid
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 20 Oct 2017 15:39:04 -0000

Sergey Chugunov created IGNITE-6695:
---------------------------------------

             Summary: Validation of joining node data consistency WRT the same data in grid
                 Key: IGNITE-6695
                 URL: https://issues.apache.org/jira/browse/IGNITE-6695
             Project: Ignite
          Issue Type: New Feature
      Security Level: Public (Viewable by anyone)
          Components: persistence
            Reporter: Sergey Chugunov


h2. Scenario
Consider the following simple scenario (persistence is active):
# Start nodes A and B, activate, add (K1, V1) to cache.
# Stop A; update K1 to (K1, V2) (only B is aware of update). Stop B.
# 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.

h2. 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.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)