Project

General

Profile

Actions

Bug #18064

closed

multisite: sync status reports master is on a different period

Added by Abhishek Lekshmanan over 7 years ago. Updated about 7 years ago.

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

0%

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

Description

On current master, sync status on secondary reports that the master is on a different period, though the master and the secondary are actually in the same period, here dc1 is the primary and dc2 is the secondary zone

$ ./bin/radosgw-admin -c ./run/dc2/ceph.conf sync status
          realm a8a09e0f-f284-43ef-bbbd-7b9d09ff214d (gold)
      zonegroup 8b93e5ac-1997-4b99-b8cc-184c683993a7 (us)
           zone f42bfb1e-aa15-4429-ae13-cbc5d1c4267c (us-west)
  metadata sync syncing
                full sync: 0/64 shards
                master is on a different period: master_period=3e6d994f-e3e8-4191-9780-6423a393e903 local_period=a2012652-9795-4550-8c0b-62b13a9a5331
                metadata is caught up with master
                incremental sync: 64/64 shards
      data sync source: 83337a5d-15c3-4e11-8bda-82d9bed80694 (us-east-1)
                        syncing
                        full sync: 0/128 shards
                        incremental sync: 128/128 shards
                        data is caught up with source

$ ./bin/radosgw-admin -c ./run/dc1/ceph.conf period get-current
{
    "current_period": "a2012652-9795-4550-8c0b-62b13a9a5331" 
}

$ ./bin/radosgw-admin -c ./run/dc2/ceph.conf period get-current                                                          
{
    "current_period": "a2012652-9795-4550-8c0b-62b13a9a5331" 
}


Related issues 2 (0 open2 closed)

Copied to rgw - Backport #18684: jewel: multisite: sync status reports master is on a different periodResolvedNathan CutlerActions
Copied to rgw - Backport #18709: kraken: multisite: sync status reports master is on a different periodResolvedNathan CutlerActions
Actions #1

Updated by Abhishek Lekshmanan over 7 years ago

Looking further into this I see that we're actually storing master_period as the first period from master instead of master's current period, since this is populated from /admin/log metadata which actually returns the first period of master. We could get master's current period and compare that instead

Actions #2

Updated by Abhishek Lekshmanan over 7 years ago

  • Status changed from New to In Progress
  • Assignee set to Abhishek Lekshmanan
Actions #4

Updated by Abhishek Lekshmanan over 7 years ago

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

Updated by Abhishek Lekshmanan about 7 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #6

Updated by Abhishek Lekshmanan about 7 years ago

  • Backport set to jewel
  • Release set to jewel
Actions #7

Updated by Loïc Dachary about 7 years ago

  • Copied to Backport #18684: jewel: multisite: sync status reports master is on a different period added
Actions #8

Updated by Abhishek Lekshmanan about 7 years ago

  • Backport changed from jewel to jewel, kraken
  • Release set to kraken
Actions #9

Updated by Nathan Cutler about 7 years ago

  • Copied to Backport #18709: kraken: multisite: sync status reports master is on a different period added
Actions #10

Updated by Nathan Cutler about 7 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF