Actions
Bug #37724
closedMDSMonitor: ignores stopping MDS that was formerly laggy
% Done:
0%
Source:
Development
Tags:
Backport:
mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDSMonitor
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
An MDS that was marked laggy (but not removed) is ignored by the MDSMonitor if it is stopping:
2018-12-20 15:13:43.187883 7f17fefd1700 1 -- 192.168.161.143:6789/0 <== mds.1 192.168.198.247:6800/1087296702 6 ==== mdsbeacon(4746/li638-125 up:stopping seq 17504 v19788) v7 ==== 400+0+0 (991254324 0 0) 0x5581581e7500 con 0x5581583e0800 2018-12-20 15:13:43.187954 7f17fefd1700 0 mon.li159-191@0(leader).mds e19788 got beacon for MDS in STATE_STOPPING, ignoring requested state change
Updated by Patrick Donnelly over 5 years ago
- Status changed from New to Fix Under Review
- Priority changed from Normal to Urgent
- Pull request ID set to 25658
Updated by Patrick Donnelly over 5 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 5 years ago
- Copied to Backport #37737: luminous: MDSMonitor: ignores stopping MDS that was formerly laggy added
Updated by Nathan Cutler over 5 years ago
- Copied to Backport #37738: mimic: MDSMonitor: ignores stopping MDS that was formerly laggy added
Updated by Patrick Donnelly about 5 years ago
- Status changed from Pending Backport to Resolved
Actions