Project

General

Profile

Actions

Bug #17899

closed

restarting an osd twice quickly enough with no other map changes can leave it running, but not up

Added by Samuel Just over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Restarting an osd twice quickly enough can result in it starting up and sending an MOSDBoot message with the same epoch as the epoch in which it was marked up_from. The mon then ignores the boot message and leaves the osd in limbo since it won't resend the boot.


Related issues 1 (0 open1 closed)

Copied to Ceph - Backport #17953: jewel: restarting an osd twice quickly enough with no other map changes can leave it running, but not upResolvedNathan CutlerActions
Actions #1

Updated by Samuel Just over 7 years ago

  • Status changed from New to Pending Backport
  • Backport set to jewel

Merge: 83ce0fe2f4f6e17a761586606813f02d1c86ebee

Actions #2

Updated by Nathan Cutler over 7 years ago

  • Copied to Backport #17953: jewel: restarting an osd twice quickly enough with no other map changes can leave it running, but not up added
Actions #3

Updated by Nathan Cutler about 7 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF