Project

General

Profile

Bug #40197

The command 'node ls' sometimes output some incorrect information about mds.

Added by shuguang wang 5 months ago. Updated 15 days ago.

Status:
Need Review
Priority:
High
Assignee:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
nautilus,mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDSMonitor
Labels (FS):
Pull request ID:
Crash signature:

Description

Env: my ceph cluster has tree nodes.Each node has one monitor and one mds and some osds.
test command: ceph node ls
Test steps:
1.test the command 'ceph node ls'. The output has information about the three MDSs.
2.Restart one mds.
3.stop the monitor which named mon.0.
4.So,the monitor which named mon.1 will be leader. Then, test the command 'ceph node ls'. The output just has information about two MDSs,without the mds who just restarted.

History

#1 Updated by Greg Farnum 5 months ago

  • Project changed from Ceph to fs
  • Category deleted (Monitor)
  • Pull request ID set to 28396

#2 Updated by Patrick Donnelly 5 months ago

  • Status changed from New to Need Review
  • Priority changed from Normal to High
  • Target version set to v15.0.0
  • Start date deleted (06/07/2019)
  • Backport set to nautilus,mimic,luminous
  • Component(FS) MDSMonitor added

#3 Updated by Min Shi 17 days ago

I repeat your steps, but the phenomenon is a little different. When I test the command `ceph node ls`, it only show the MDS that I just restart now. And at this time, the leader monitor and restarted mds are in same node. Then things get strange, I just recurrent one time, then I repeat about 5 times, this command's output is normal.

#4 Updated by Min Shi 15 days ago

Min Shi wrote:

I repeat your steps, but the phenomenon is a little different. When I test the command `ceph node ls`, it only show the MDS that I just restart now. And at this time, the leader monitor and restarted mds are in same node. Then things get strange, I just recurrent one time, then I repeat about 5 times, this command's output is normal.

I now can stablely recurrent this phenomenon.

Also available in: Atom PDF