Task #1182
Story #1388: implement MN-MN replication manager in CN stack
Implement setReplicationStatus() in CN service
100%
Description
setReplicationStatus() is called by a Member Node to indicate progress on an object replication request. The process is described in UC09 ( http://mule1.dataone.org/ArchitectureDocs-current/design/UseCases/09_uc.html ) and http://mule1.dataone.org/ArchitectureDocs-current/apis/cn_api_data_replication.html#CN_data_replication.setReplicationStatus
History
#1 Updated by Robert Waltz almost 14 years ago
- Category set to d1_cn_service
- Milestone set to CCI-0.5
#2 Updated by Robert Waltz almost 14 years ago
- Target version changed from Sprint-2011.05 to Sprint-2011.06
#3 Updated by Robert Waltz almost 14 years ago
- Target version changed from Sprint-2011.05 to Sprint-2011.06
#4 Updated by Robert Waltz over 13 years ago
- Assignee changed from Robert Waltz to Rob Nahf
#5 Updated by Robert Waltz over 13 years ago
- Assignee changed from Rob Nahf to Robert Waltz
#6 Updated by Robert Waltz over 13 years ago
- Parent task changed from #1132 to #1388
#7 Updated by Robert Waltz over 13 years ago
- Milestone deleted (
CCI-0.5)
#8 Updated by Robert Waltz over 13 years ago
- Category changed from d1_cn_service to d1_replication
- Assignee changed from Robert Waltz to Chris Jones
- Milestone set to CCI-0.7.0
#9 Updated by Chris Jones about 13 years ago
- Assignee changed from Chris Jones to Nicholas Dexter
ReplicationService needs to call setReplicationStatus to QUEUED after the hzReplicationTasks.put() method is called. ReplicationTask.call() needs to set it to REQUESTED after the call to MNReplication.replicate(). When the MN calls setReplicationStatus (to set it to COMPLETE), ReplicationService must first validate the checksums, and set it to COMPLETE or to INVALIDATED if the don't match. That would complete the cycle for the given ReplicationTask.
#10 Updated by Chris Jones about 13 years ago
- Assignee changed from Nicholas Dexter to Chris Jones
I'll take this one.
#11 Updated by Chris Jones about 13 years ago
- Status changed from New to Closed
Implemented in ReplicationService, however it currently uses a shared Hazelcast Node Map for node lookups, which currently doesn't exist. If the map is not available, we'll revert to using the D1Client REST calls to get Node information.
