Project

General

Profile

Actions

Feature #15371

closed

Delayed rbd-mirror replication support

Added by Jason Dillaman about 8 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Allow an administrator to configure a time-delay for rbd-mirror asynchronous replication (e.g. the non-primary site is X hours behind the primary site).

Actions #1

Updated by Mykola Golub over 7 years ago

  • Status changed from New to In Progress
  • Assignee set to Mykola Golub
Actions #2

Updated by Mykola Golub over 7 years ago

  • Status changed from In Progress to Fix Under Review
Actions #3

Updated by Jason Dillaman over 7 years ago

  • Status changed from Fix Under Review to Resolved
Actions #4

Updated by liuzhong chen about 6 years ago

I wonder the delay for the non-primary,this may make a poor RPO。

Actions #5

Updated by liuzhong chen about 6 years ago

there is any advantage for this delay?

Actions #6

Updated by Jason Dillaman about 6 years ago

@liuzhong chen: indeed -- while it's use-case dependent, it's possible you might want to ensure that the backup site is always X hours behind the primary site just in case you want to provide a window to recover from a destructive change to the primary.

Actions #7

Updated by liuzhong chen about 6 years ago

Jason Dillaman wrote:

@liuzhong chen: indeed -- while it's use-case dependent, it's possible you might want to ensure that the backup site is always X hours behind the primary site just in case you want to provide a window to recover from a destructive change to the primary.

@Jason Borden Dillaman Thanks,I understand this this patch meaning.

Actions

Also available in: Atom PDF