Project

General

Profile

Task #4098

Synchronization should allow valid replicas held by MNs to set obsoletedBy and archive flags

Added by Robert Waltz almost 9 years ago. Updated about 8 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
d1_synchronization
Target version:
-
Start date:
2012-07-12
Due date:
2013-09-07
% Done:

0%

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

Description

Need to discuss what Matt has to say about client-MN interactions of Morpho. Someone may have update capability on an object but not have permission to modify on the authoritative MN.

History

#1 Updated by Robert Waltz almost 9 years ago

  • Parent task set to #3910

#2 Updated by Robert Waltz almost 9 years ago

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

#3 Updated by Robert Waltz almost 9 years ago

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

#4 Updated by Robert Waltz almost 9 years ago

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

#5 Updated by Dave Vieglais over 8 years ago

  • Target version deleted (2013.46-Block.6.2)

#6 Updated by Robert Waltz about 8 years ago

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

#7 Updated by Robert Waltz about 8 years ago

  • Target version set to 2014.30-Block.4.3

#8 Updated by Robert Waltz about 8 years ago

  • Assignee changed from Robert Waltz to Skye Roseboom

#9 Updated by Robert Waltz about 8 years ago

  • Product Version changed from 1.4.0 to *
  • Parent task deleted (#3910)
  • Priority changed from High to Normal
  • Milestone changed from CCI-1.4 to None
  • Assignee changed from Skye Roseboom to Dave Vieglais

Deferred until we can clarify this issue.

Also, we have no way of locking the object on a replicated node. In V2, if MemberNodes control systemMetadata then the authoritative Membernode should be the membernode modifying the systemMetadata and not a archival membernode.

This request hinges on DataONE's distributed architecture, whether DataONE Membernodes form an LOCKS system, a Peer-to-Peer network, or a Computer Cluster. Each architecture has its own set of problems that need to be addressed.

#10 Updated by Robert Waltz about 8 years ago

  • Target version deleted (2014.30-Block.4.3)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)