Project

General

Profile

Task #7134

Story #6721: Update replication and replication auditing for v2 API changes

Update replication component to encapsulate use of V1, V2 replication API and communication depending on MN support

Added by Skye Roseboom almost 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_replication
Target version:
Start date:
2015-05-28
Due date:
% Done:

100%

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

Description

If MN supports V2, use V2 replication REST endpoints and V2 communication objects from libclient.

History

#1 Updated by Skye Roseboom almost 9 years ago

  • Category set to d1_replication

#2 Updated by Chris Jones over 8 years ago

  • Assignee changed from Skye Roseboom to Chris Jones

#3 Updated by Skye Roseboom about 8 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
  • translation missing: en.field_remaining_hours set to 0.0

Ben did some v1 and v2 replication communication work. I worked on the replication target determination logic so replicas are placed in appropriate MN (v1, v2). replication working properly in production.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)