Project

General

Profile

Bug #8640

Story #8639: Replication performance is too slow to service demand

Replication includes "down" nodes as replication targets

Added by Dave Vieglais over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
d1_replication
Target version:
-
Start date:
2018-07-04
Due date:
% Done:

0%

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

Description

The call sequence to get the list of target nodes is roughly:

ReplicationManager.processPid()
ReplicationManager.getPotentialTargetNodes()
ReplicationManager.getNodeReferences()
NodeRegistryServiceImpl.listNodes()
NodeFacade.getApprovedNodeList()
NodeAccess.getApprovedNodeList()

It does not appear that the up/down status of a node is examined. Seems the appropriate place to do this would be in ReplicationManager.getPotentialTargetNodes() as this is where previous attempts are examined and the node rejected if too many failures are reported in a time period. Having a check for node up/down status here is logical.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)