Project

General

Profile

Actions

Bug #53436

closed

mds, mon: mds beacon messages get dropped? (mds never reaches up:active state)

Added by Venky Shankar over 2 years ago. Updated over 2 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Correctness/Safety
Target version:
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS, MDSMonitor
Labels (FS):
task(medium)
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Seen in this run - https://pulpito.ceph.com/vshankar-2021-11-24_07:14:27-fs-wip-vshankar-testing-20211124-094330-testing-default-smithi/6524013/

Didn't analyze in depth, but looks like the mds (mds.d) sent a beacon message wanting "up:active" state to the monitor (mon.a), however, the monitor never received this beacon thereby leaving the mds in "up:creating" state.

AFAICS, there was no monitor crash or failover.


Related issues 2 (1 open1 closed)

Related to RADOS - Bug #45647: "ceph --cluster ceph --log-early osd last-stat-seq osd.0" times out due to msgr-failures/many.yamlNew

Actions
Related to RADOS - Bug #39039: mon connection reset, command not resentDuplicateSage Weil

Actions
Actions

Also available in: Atom PDF