Project

General

Profile

Task #1786

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

Use Hazelcast ExecutorService to update remote CN Metacat Science Metadata

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

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

0%

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

Description

Science Metadata must also be replicated across the CNs, and the current Metacat implementation provides a serial queue to process replication events one by one. To facilitate parallel replication across CNs, use the Hazelcast ExecutorService to submit CNReplicationTasks to each of the CNs in the cluster. The PID should be locked until the task is finished for the science metadata object. Although we can submit to a Set of hazelcast members at once with one task, it may be better to iterate over the set and submit the task to each member in order to individually manage locks and failures for each CN.

History

#1 Updated by Chris Jones about 12 years ago

  • Status changed from New to Rejected

Metacat's replication system is currently being used for syncing science metadata, so this won't be implemented at the moment.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)