Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This page is based on 'Conflict detection and resolution - research'.

Introduction

Conflict scenarios:

  • Update-update
    Occurs when the same object was updated at more than one node.
  • Update-delete
    Occurs if a row was updated at one node, but the same row was deleted at another node.
  • Delete-delete
    Occurs when a row was deleted from more than one node.

Conflict Detection

We need a new table in a database of each instance to store hash codes of objects pulled from this instance's Parent.

PULL:

  1. At first, when we pull an object from Parent to Child instance (where it does not exist yet):
    1. calculate hash code of an object pulled from Parent,
    2. look for an object on Child instance with UUID of pulled object,
    3. such object on Child instance does not exist, so object is created on Child instance,
    4. object's hash code is saved in Child's database as the latest version of this object on Parent instance,
    5. there is NO conflict.
  2. Object is NOT modified on Parent instance.
  3. When we pull the same object from Parent the second time (this object already exist on Child instance):
    1. calculate hash code of an object pulled from Parent,
    2. look for an object on Child instance with UUID of pulled object,
    3. such object on Child instance exists, so compare calculated hash code with a hash code that is saved in Child's database,
    4. they are equal, which means that object on Child instance is up to date with corresponding object on Parent instance,
    5. there is NO conflict.
  4. Object is modified both on Parent and/or Child instance.
  5. When we pull the same object from Parent the third time (this object already exist on Child instance):
    1. calculate hash code of an object pulled from Parent,
    2. look for an object on Child instance with UUID of pulled object,
    3. such object on Child instance exists, so compare calculated hash code with a hash code that is saved in Child's database,
    4. they are NOT equal, which means that object on Child instance is NOT up to date with corresponding object on Parent instance
    5. there is a conflict, which is resolved using rule RULE 1


PUSH:


  1. At first, when we push an object from Child to Parent instance (where it does not exist yet):
    1. In SyncPushServiceImpl class during execution of readAndPushObjectToParent method we call shouldPushObject method, where we pull corresponding object from Parent instance,
    2. this object does not exist on Parent instance yet, shouldPushObject returns true,
    3. object is pushed to Parent,
    4. object's hash code is saved in Child's database as the latest version of this object on Parent instance.
  2. Object is modified on Child instance.
  3. When we push this object from Child to Parent instance (where it already exists):
    1. In SyncPushServiceImpl class during execution of readAndPushObjectToParent method we call shouldPushObject method, where we pull corresponding object from Parent instance,
    2. this object already exists on Parent instance,
    3. calculate hash code of an object pulled from Parent,
    4. compare calculated hash code with a hash code that is saved in Child's database,
    5. they are equal, which means that Child modified the latest version of object on Parent instance,
    6. object is pushed to Parent,
    7. object's hash code is updated in Child's database as the last version of this object.
  4. Object is modified both on Parent and/or Child instance.
  5. When we push this object from Child to Parent instance (where it already exists):
    1. In SyncPushServiceImpl class during execution of readAndPushObjectToParent method we call shouldPushObject method, where we pull corresponding object from Parent instance,
    2. this object already exists on Parent instance,
    3. calculate hash code of an object pulled from Parent,
    4. compare calculated hash code with a hash code that is saved in Child's database,
    5. they are NOT equal, which means that object on Child instance is NOT up to date with corresponding object on Parent instance (someone modified this object on Parent instance),
    6. there is a conflict, which is resolved using rule RULE 2.

Conflict Resolution

PULL:

  • RULE 1

    If hash code of an object on Parent instance is NOT equal to hash code of an object on Child instance* it means that there is a new version of this object on Parent → 

    • if object on Child instance was NOT modified (calculated hash code of modified object is equal to hash code saved on Child's instance*) →
      • void current object's fields on Child instance,
      • save fields of object from Parent instance to Child.

    • if object on Child instance was modified (calculated hash code of modified object is NOT equal to hash code saved on Child's instance*) → 
      • these two objects have to be merged**, then
      • saved on Child and Parent instance;
      • hash codes on both Child and Parent instance have to be updated.


* REMEMBER: This is a hash code of an object that was calculated and saved on the last pull of this object from Parent. This hash code is stored in a separate table than pulled object.

** See Merge

PUSH:

  • RULE 2

    If hash code of an object on Parent instance is NOT equal to hash code of an object on Child instance* it means that the object was updated on Parent instance after the last pull to Child (we are pushing modifications of outdated version of object) → 

    • if object on Child instance was NOT modified (calculated hash code of modified object is equal to hash code saved on Child's instance*) → PUSH operation of this object will not take place

    • if object on Child instance was modified (calculated hash code of modified object is NOT equal to hash code saved on Child's instance*) → 
      • these two objects have to be merged**, then
      • saved on Child and Parent instance;
      • hashcodes on both Child and Parent instance have to be updated.


* REMEMBER: This is a hashcode of an object that was calculated and saved on the last pull of this object from Parent. This hash code is stored in a separate table than pulled object.

** See Merge

Merge

Once a conflict was detected two objects will have to be merged. To do this, a new database table "Conflicts" will have to be created.
This table will have columns: openmrs_class, first_object, second_object and more if needed.

It will be possible to insert any type of object into child_object and parent_object due to its type: it will be either JSON, (TINY)BLOB, TEXT or else.


All conflicted objects will be put into this table and queued just like AuditLog does this.
However, there should be only the most recent merge conflict for any object. The old ones should be voided.

Then either chosen strategy or UI will be used to:

  • determine if child_object, parent_object or mixed object will be preserved,
  • determine what operation should be taken after merging (push / pull / ...)

When the conflict is resolved we should save parent's object as voided in child's database.


UI for merging will use openmrs_class field to determine what class are child_object and parent_object.
Fields of determined class will be displayed as text-boxes or buttons for each of two objects.
User will be able to choose which value he wants to keep.


  • No labels