Incorporate Node Replication Policy into replication processing
Once MN replication policy are available through the Node Repository datasource, replication processing will need to be updated to honor this default replication policy when items without any policy are synchronized to the CN.
This task needs to follow redmine #2192.
#4 Updated by Rob Nahf over 9 years ago
- % Done changed from 0 to 20
- Assignee set to Rob Nahf
implementing in ReplicationManager class in trunk (v2.0).
It would be interesting to create a NodeRegistry query to return the set of possible nodes for a given object, but are probably constrained to use the hazelcast-backed map of Nodes, because that's where we are getting our systemMetadata. so I'll continue to use that structure.
Need to determine if the PreferredMemberNode list is ordered or unordered, and if we need any 'distribution' across preferred nodes.
#5 Updated by Rob Nahf about 9 years ago
- Status changed from New to In Progress
this became a complicated task, because ReplicationManager tests were commented out (over a year ago), and some v2 changes have been subsequently committed. Will have to rehabilitate the tests before being able to test the new strategy. I'm creating subtasks for these.