Project

General

Profile

Task #3062

Story #3910: Modify Synchronization to apply more validation Logic

Synchronization should not change the Authoritative member node property of SystemMetadata

Added by Robert Waltz over 12 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
High
Assignee:
Skye Roseboom
Category:
d1_synchronization
Target version:
CCI-1.5.0
Start date:
2012-07-12
Due date:
2013-09-07
% Done:

100%

Estimated time:
0.00 h
Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

Does the CN have the right to assign Authoritative member node. Ben says no. The other membernode may be authoritative.

Updates to obsoletedBy and archive flags may only be from authoritative membernodes.

authoritativeMN must be set by the MemberNode- LTER may have replica information for other MNs that may be synchronized first.

if the authoritative memberNode is not originMember node, then it is considered a replica.

Replica's may not be created before the original Object is synchronized from the Authoritative membernode. CN V1 does not have a way to update systemMetadata, so if jthe replica is created, then any systemMetadata information contained in the replica will be definitive for the original object. (e.g. OriginMember node will always be listed as the replica membernode and not the true origin of the object).

History

#1 Updated by Robert Waltz over 12 years ago

  • Status changed from New to In Progress

#2 Updated by Robert Waltz over 12 years ago

  • Milestone changed from CCI-1.0.3 to CCI-1.0.4

#3 Updated by Robert Waltz over 12 years ago

  • Target version changed from Sprint-2012.29-Block.4.3 to Sprint-2012.33-Block.5.1

#4 Updated by Robert Waltz about 12 years ago

CCIT Meeting. Ben mentioned that this may not be a desirable outcome.

#5 Updated by Robert Waltz about 12 years ago

  • Priority changed from Normal to High

#6 Updated by Robert Waltz about 12 years ago

  • Target version changed from Sprint-2012.33-Block.5.1 to Sprint-2012.35-Block.5.2

#7 Updated by Robert Waltz about 12 years ago

  • Milestone changed from CCI-1.0.4 to CCI-1.0.5
  • Target version changed from Sprint-2012.35-Block.5.2 to Sprint-2012.37-Block.5.3

#8 Updated by Robert Waltz about 12 years ago

  • Target version changed from Sprint-2012.37-Block.5.3 to Sprint-2012.39-Block.5.4

#9 Updated by Robert Waltz about 12 years ago

  • Milestone changed from CCI-1.0.5 to CCI-1.1

#10 Updated by Robert Waltz about 12 years ago

  • Target version changed from Sprint-2012.39-Block.5.4 to Sprint-2012.44-Block.6.2
  • Milestone changed from CCI-1.1 to CCI-1.1.1
  • translation missing: en.field_remaining_hours set to 0.0
  • Due date set to 2012-11-10

#11 Updated by Robert Waltz almost 12 years ago

  • Target version changed from Sprint-2012.44-Block.6.2 to Sprint-2012.50-Block.6.4
  • Due date changed from 2012-11-10 to 2013-01-05

#12 Updated by Robert Waltz almost 12 years ago

  • Target version changed from Sprint-2012.50-Block.6.4 to 2013.2-Block.1.1
  • Due date changed from 2013-01-05 to 2013-01-19

#13 Updated by Robert Waltz over 11 years ago

  • Target version changed from 2013.2-Block.1.1 to 2013.10-Block.2.1
  • Due date changed from 2013-01-19 to 2013-03-16

#14 Updated by Robert Waltz over 11 years ago

  • Milestone changed from CCI-1.1.1 to CCI-1.1.2
  • Due date changed from 2013-03-16 to 2013-06-22
  • Target version changed from 2013.10-Block.2.1 to 2013.24-Block.3.4

#15 Updated by Robert Waltz over 11 years ago

  • Due date changed from 2013-06-22 to 2013-08-03
  • Target version changed from 2013.24-Block.3.4 to 2013.30-Block.4.3

#16 Updated by Robert Waltz over 11 years ago

  • Milestone changed from CCI-1.1.2 to CCI-1.3
  • Target version changed from 2013.30-Block.4.3 to 2013.35-Block.5.1
  • Due date changed from 2013-08-03 to 2013-09-07
  • Parent task set to #3910

#17 Updated by Robert Waltz about 11 years ago

  • Subject changed from Synchronization should allow valid replicas held by MNs to set obsoletedBy and archive flags to Synchronization should not change the Authoritative member node property of SystemMetadata
  • Product Version set to 1.2.0
  • Milestone changed from CCI-1.3 to CCI-1.2
  • Estimated time set to 0.00
  • Description updated (diff)

#18 Updated by Robert Waltz about 11 years ago

  • Milestone changed from CCI-1.2 to CCI-1.3
  • Product Version changed from 1.2.0 to 1.3.0

#19 Updated by Robert Waltz about 11 years ago

  • Target version changed from 2013.35-Block.5.1 to 2013.44-Block.6.1

#20 Updated by Robert Waltz about 11 years ago

  • Milestone changed from CCI-1.3 to CCI-1.2
  • Product Version changed from 1.3.0 to 1.2.1

#21 Updated by Robert Waltz about 11 years ago

  • Target version changed from 2013.44-Block.6.1 to 2013.46-Block.6.2

#22 Updated by Matthew Jones about 11 years ago

IMO, the CN should not be changing the AuthoritativeMN. In addition, the OriginMN should never be changed, by anybody. The OriginMN was defined as the MN on which the data was originally created, and is meant as a metadata tracker to know which MN originated an object even if that object no longer exists on that MN or if that MN is no longer Authoritative. The statements in the description of this ticket that one can infer replica status based on the origin MN are wrong; an object is a replica if and only if it is a copy on a MN that is not the AuthoritativeMN.

#23 Updated by Dave Vieglais almost 11 years ago

  • Target version deleted (2013.46-Block.6.2)

#24 Updated by Robert Waltz over 10 years ago

  • Product Version changed from 1.2.1 to 1.4.0
  • Milestone changed from CCI-1.2 to CCI-1.4

#25 Updated by Robert Waltz over 10 years ago

  • Target version set to 2014.30-Block.4.3

#26 Updated by Robert Waltz over 10 years ago

  • Assignee changed from Robert Waltz to Skye Roseboom

#27 Updated by Skye Roseboom about 10 years ago

  • Target version changed from 2014.30-Block.4.3 to Release Backlog

#28 Updated by Robert Waltz about 10 years ago

  • Product Version changed from 1.4.0 to *

#29 Updated by Robert Waltz about 10 years ago

  • Target version changed from Release Backlog to CCI-1.4.1

#30 Updated by Robert Waltz about 10 years ago

  • Target version changed from CCI-1.4.1 to CCI-1.4.2

#31 Updated by Robert Waltz about 10 years ago

  • Target version changed from CCI-1.4.2 to CCI-1.5.0

#32 Updated by Skye Roseboom about 10 years ago

  • Milestone changed from CCI-1.4 to None

#33 Updated by Skye Roseboom about 10 years ago

  • Status changed from In Progress to Testing

#34 Updated by Skye Roseboom almost 10 years ago

  • Status changed from Testing to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)