Project

General

Profile

Task #5329

The default value of metacat timed-replication is off in CN

Added by Jing Tao almost 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_cn_buildout
Target version:
-
Start date:
2014-05-21
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

I believe CNs use metacat replication to synchronize data and metadata objects. Metadata has two replication mechanisms: forced and timed replication.

Forced replication happens when a new content comes, it notifies the remote server to get it. If the remote server is off line. The forced replication will fail. However, the timed the replication may fix the failure. Timed the replication happens at the particular time, e.g. 3 am every day. At the 3 a.m., the remote server is up and timed replication happens. The missed new documents will be replicated to the remote server by the timed replication.

However, the cn set the value to be off:
replication.timedreplication=false

I think we should change it to be true.

Any comments?

History

#1 Updated by Robert Waltz almost 10 years ago

Yes, I believe the value should be turned on by default.

#2 Updated by Jing Tao over 9 years ago

  • Status changed from New to Closed
  • translation missing: en.field_remaining_hours set to 0.0

The code to set the value to be true was added to the trunk.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)