Project

General

Profile

Bug #52975

MDSMonitor: no active MDS after cluster deployment

Added by Igor Fedotov over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Urgent
Category:
Correctness/Safety
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
pacific
Regression:
Yes
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDSMonitor
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

This happens starting v16.2.6 if CephFS volume creation and setting allow_standby_replay mode occur before MDS daemons creation.
E.g. the attached vstart patch produces a new cluster with all MDS-es marked as standby.

p1.diff View (2.11 KB) Igor Fedotov, 10/19/2021 02:27 PM


Related issues

Duplicated by CephFS - Bug #52094: Tried out Quincy: All MDS Standby Duplicate
Copied to CephFS - Backport #53232: pacific: MDSMonitor: no active MDS after cluster deployment Resolved

History

#1 Updated by Igor Fedotov over 2 years ago

This behavior isn't present in 16.2.5.

#2 Updated by Venky Shankar over 2 years ago

  • Assignee set to Venky Shankar

#3 Updated by Venky Shankar over 2 years ago

  • Category set to Correctness/Safety
  • Target version set to v17.0.0
  • Component(FS) MDS added

#4 Updated by Venky Shankar over 2 years ago

  • Backport set to pacific,octopus

#5 Updated by Venky Shankar over 2 years ago

Thanks for the reproducer Igor.

commit cbd9a7b354abb06cd395753f93564bdc687cdb04 ("mon,mds: use per-MDS compat to inform replacement") seems to be the breaking this.

#6 Updated by Patrick Donnelly over 2 years ago

  • Subject changed from No active MDS after cluster deployment to MDSMonitor: no active MDS after cluster deployment
  • Status changed from New to In Progress
  • Assignee changed from Venky Shankar to Patrick Donnelly
  • Source set to Development
  • Backport changed from pacific,octopus to pacific
  • Component(FS) MDSMonitor added
  • Component(FS) deleted (MDS)

#7 Updated by Patrick Donnelly over 2 years ago

  • Status changed from In Progress to Fix Under Review
  • Priority changed from Normal to Urgent
  • Pull request ID set to 43851

#8 Updated by Patrick Donnelly over 2 years ago

  • Status changed from Fix Under Review to Pending Backport

#9 Updated by Backport Bot over 2 years ago

  • Copied to Backport #53232: pacific: MDSMonitor: no active MDS after cluster deployment added

#10 Updated by Patrick Donnelly over 2 years ago

  • Duplicated by Bug #52094: Tried out Quincy: All MDS Standby added

#11 Updated by Loïc Dachary over 2 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