Story #8639
Replication performance is too slow to service demand
Start date:
2018-07-04
Due date:
% Done:
0%
Story Points:
20
Sprint:
Description
The replication process is operating too slowly to service demand resulting in lengthy delays to completion of replication tasks for new and changed content.
This is particularly apparent in the stage environment where perhaps the number of orphaned objects and deprecated / defunct nodes is interfering with expected behaviors.
Goal of this story is to identify and address the immediate issues. Any significant refactoring of the replication process should be captured under another story / epic.
Subtasks
Related issues
History
#1 Updated by Dave Vieglais almost 6 years ago
- Assignee changed from Jing Tao to Chris Jones
#2 Updated by Dave Vieglais almost 6 years ago
- Related to Task #8482: ESSDIVE: Test Registration added
#3 Updated by Dave Vieglais almost 6 years ago
- Related to Story #8162: Replication tasks can contain stale potential target nodes added
#4 Updated by Dave Vieglais almost 6 years ago
- Related to Story #7650: DAO for SystemMetadata changes the SystemMetadata.replicationPolicy added
#5 Updated by Dave Vieglais almost 6 years ago
- Related to Story #6377: Review CNode initialization in ReplicationManager - it doesn't use local CN reference added
#6 Updated by Dave Vieglais almost 6 years ago
- Related to Story #4463: Incorporate Node Replication Policy into replication processing added
