Project

General

Profile

Actions
Copy link

Bug #59645

open

Multi site synchronisation: In an active-active arrangement, secondary sync status reports 'data is caught up with source' but no primary data sync information

Added by Utkarsh Bhatt 12 months ago.

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

0%

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

Description

We are running a ceph cluster with Ubuntu Lunar + Ceph Quincy (17.2.5) and observed a sync status discrepancy between primary and secondary cluster.

secondary sync status:
realm 096e9ed2-0466-4546-9de7-f80fe51d5cc1 (zaza_realm)
zonegroup 68f03c1e-eb6c-4d11-87bb-d57ddb9a58fe (zaza_zg)
zone c1504149-124f-44b8-a7d6-ff108ca9d825 (zaza_secondary)
metadata sync syncing
full sync: 0/64 shards
incremental sync: 64/64 shards
metadata is caught up with master
data sync source: c42b03f2-7d25-447e-9079-d5d4e5a713e5 (zaza_primary)
syncing
full sync: 0/128 shards
incremental sync: 128/128 shards
data is caught up with source

primary sync status:
realm 096e9ed2-0466-4546-9de7-f80fe51d5cc1 (zaza_realm)
zonegroup 68f03c1e-eb6c-4d11-87bb-d57ddb9a58fe (zaza_zg)
zone c42b03f2-7d25-447e-9079-d5d4e5a713e5 (zaza_primary)
metadata sync no sync (zone is master)

Interestingly there is no ceph log artefact at the primary rgw machine, have attached the same from the secondary.

Files

secondary-ceph-rgw.log (539 KB) secondary-ceph-rgw.log Ceph RGW log artefact from secondary site Utkarsh Bhatt, 05/04/2023 02:07 PM

No data to display

Actions
Copy link

Also available in: Atom PDF