Project

General

Profile

Bug #43360

multisite: sync status doesn't say which shard is furthest behind

Added by Casey Bodley over 4 years ago. Updated about 4 years ago.

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

0%

Source:
Tags:
multisite
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The 'radosgw-admin sync status' command gives you a timestamp for "oldest incremental change not applied", but doesn't tell you which shard it came from.


Related issues

Copied to rgw - Backport #43372: nautilus: multisite: sync status doesn't say which shard is furthest behind Resolved

History

#1 Updated by Casey Bodley over 4 years ago

  • Status changed from New to Pending Backport
  • Tags set to multisite
  • Backport changed from multisite to nautilus
  • Pull request ID set to 32311

#2 Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #43372: nautilus: multisite: sync status doesn't say which shard is furthest behind added

#3 Updated by Nathan Cutler about 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF