Project

General

Profile

Story #3474

Maintain consistency across CN hazelcast backing datastores

Added by Chris Jones about 11 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
performance-scalability
Target version:
Start date:
2013-01-16
Due date:
2014-03-29
% Done:

0%

Story Points:
Sprint:

Description

Story to capture work needed ensure data consistency across CN datastores.

Due to partition tolerance of the distributed cache (hazelcast), it is possible for the storage datastore to become inconsistent across CN when create/update/deletes are performed in one cluster partition and not synchronized across the cluster when the partitions in the cluster are resolved/joined.


Subtasks

Task #3488: Create custom merge policy to support managing data/information inconsistencyNewChris Jones


Related issues

Related to Infrastructure - Story #3736: CN Consistency Check and CN Recovery Rejected

History

#1 Updated by Skye Roseboom about 11 years ago

  • Subject changed from Create a custom merge policy class to maintain consistency across nodes to Maintain consistency across CN hazelcast backing datastores
  • Parent task deleted (#3470)

Story to capture work needed ensure data consistency across CN datastores.

Due to partition tolerance of the distributed cache (hazelcast), it is possible for the storage datastore to become inconsistent across CN when create/update/deletes are performed in one cluster partition and not synchronized across the cluster when the partitions in the cluster are resolved/joined.

#2 Updated by Skye Roseboom about 11 years ago

  • Description updated (diff)

#3 Updated by Skye Roseboom about 11 years ago

  • Target version changed from 2013.2-Block.1.1 to 2013.4-Block.1.2

#4 Updated by Skye Roseboom about 11 years ago

  • Tracker changed from Task to Story
  • Due date set to 2013-02-02
  • translation missing: en.field_remaining_hours set to 0.0

#5 Updated by Skye Roseboom about 11 years ago

  • Assignee changed from Skye Roseboom to Chris Jones

#6 Updated by Robert Waltz about 11 years ago

  • Due date changed from 2013-02-02 to 2013-03-16
  • Target version changed from 2013.4-Block.1.2 to 2013.10-Block.2.1

#7 Updated by Chris Jones almost 11 years ago

  • Due date changed from 2013-03-16 to 2013-06-08
  • Target version changed from 2013.10-Block.2.1 to 2013.22-Block.3.3

#8 Updated by Chris Jones over 10 years ago

  • Target version changed from 2013.22-Block.3.3 to 2013.35-Block.5.1
  • Due date changed from 2013-06-08 to 2013-09-07

#9 Updated by Chris Jones about 10 years ago

  • Target version changed from 2013.35-Block.5.1 to 2014.2-Block.1.1
  • Due date changed from 2013-09-07 to 2014-01-18

#10 Updated by Chris Jones about 10 years ago

  • Target version changed from 2014.2-Block.1.1 to 2014.12-Block.2.2
  • Due date changed from 2014-01-18 to 2014-03-29

#11 Updated by Chris Jones almost 10 years ago

  • Status changed from New to Rejected

Due to the larger architectural scope of the consistency issues with Hazelcast over WAN, a custom merge policy within hazelcast won't provide a complete fix. I'm rejecting this in favor of an architectural refactor that will be described in other tickets.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)