Project

General

Profile

Task #1787

Task #1782: CN Replication components should be separated for scalability

Create a callable CNReplicationTask class for remote execution

Added by Chris Jones over 12 years ago. Updated about 12 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Metacat
Target version:
-
Start date:
2011-09-11
Due date:
% Done:

0%

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

Description

As in org.dataone.cn.service.replication.v1.ReplicationTask class (should be renamed to MNReplicationTask), we need a CNReplicationTask for remote updates to System Metadata and Science Metadata in Metacat. The class must also implement Serializable, and so may only include member variables that are D1 types defined in the schema and other XML-based objects. Some XML instances may include data inline (like EML), but they are in CDATA sections and can't include binary data.
Test whether or not a Hazelcast map can be used for science metadata. The map could be set to a 100% eviction policy so that no entries stay in memory, but would be available via a backing-store class. This may not be needed since distributed tasks are still necessary to updated remote CN Metacat backing stores.

History

#1 Updated by Chris Jones about 12 years ago

  • Status changed from New to Rejected

CNReplicationTask is no longer needed since Metacat listeners update the backend Metacat database on entry added/updated events.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)