Project

General

Profile

Bug #16894

multisite: metadata master can get the wrong value for 'oldest_log_period'

Added by Casey Bodley 11 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
08/02/2016
Due date:
% Done:

0%

Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Release:
Needs Doc:
No

Description

When the metadata master starts up, it goes backwards through its per-period metadata logs until it finds a period with no log shards (stat returns ENOENT on all shards). It returns the period after that as it's oldest_log_period, and other zones start their sync at that point.

But it's possible and likely that intermediate periods only introduce realm configuration changes, and don't have any associated changes in the metadata log. So we'll skip past any logs that came before that, and advertise the wrong oldest_log_period to our peers.


Related issues

Copied to rgw - Backport #17512: jewel: multisite: metadata master can get the wrong value for 'oldest_log_period' Resolved

History

#1 Updated by Casey Bodley 11 months ago

  • Status changed from In Progress to Need Review

#2 Updated by Yehuda Sadeh 9 months ago

  • Status changed from Need Review to Pending Backport
  • Needs Doc set to No

#3 Updated by Nathan Cutler 9 months ago

  • Copied to Backport #17512: jewel: multisite: metadata master can get the wrong value for 'oldest_log_period' added

#4 Updated by Nathan Cutler 5 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF