Project

General

Profile

Task #1782

CN Replication components should be separated for scalability

Added by Chris Jones over 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Chris Jones
Category:
d1_replication
Target version:
-
Start date:
2011-09-11
Due date:
% Done:

100%

Milestone:
CCI-0.6.4
Product Version:
*
Story Points:
Sprint:

Description

Currently, org.dataone.cn.service.replication.v1.ReplicationService implements the CNReplication API to field REST calls from both MNs and CNs, and also the Hazelcast EntryListener and ItemListener interfaces to monitor changes to 1) the hzSystemMetadataMap and 2) the hzReplicationTasks queue.
This class should be refactored into 1) a ReplicationManager class that implements the Hazelcast interfaces and creates and submits ReplicationTasks, and 2) a ReplicationService (implemented in edu.ucsb.nceas.metacat.dataone.CNodeService) that handles the REST calls.

Subtasks

Task #1783: Create the ReplicationManager class to manage MN ReplicationTasksClosedChris Jones

Task #1790: Create ReplicationManagerTest class to test ReplicationManagerClosedNicholas Dexter

Task #1784: Implement CNReplication in Metacat's CNodeService using HazelcastRejectedChris Jones

Task #1785: CN SystemMetadata synchronization when an offline CN comes onlineRejectedBen Leinfelder

Task #1786: Use Hazelcast ExecutorService to update remote CN Metacat Science MetadataRejectedChris Jones

Task #1787: Create a callable CNReplicationTask class for remote executionRejectedChris Jones

Task #1788: Create a CNReplication tier 4 integration testClosedChris Jones

Task #1789: Integrate replication queues and maps into Hazelcast processing clusterClosedRobert Waltz

History

#1 Updated by Chris Jones almost 13 years ago

  • Status changed from New to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)