Project

General

Profile

Bug #50813

mon/OSDMonitor: should clear new flag when do destroy

Added by Zengran Zhang almost 3 years ago. Updated almost 3 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

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

Description

the new flag in osdmap will affects the osd up according option
mon_osd_auto_mark_new_in. So it is more safe to clear the new flag when
destroy osd. the follow sequence may cause new osd can not up.

1. ceph osd new
2. do not start daemon, so the new flag will exist.
3. ceph osd destroy the osd, the destoryed flag add, but new flag
remain to exist. then the new state is :
"state": [
"destroyed",
"exists",
"new"
]
5. if we new the osd again, the new flag will flip ,and the state will become:
"state": [
"exists",
]
6. becase the new flag do not exist, so the osd boot and can not up when
the option mon_osd_auto_mark_new_in is true

History

#1 Updated by Neha Ojha almost 3 years ago

  • Project changed from Ceph to RADOS
  • Category deleted (OSDMap)

#2 Updated by Neha Ojha almost 3 years ago

  • Status changed from New to Fix Under Review
  • Assignee set to Zengran Zhang
  • Pull request ID set to 41336

#3 Updated by Zengran Zhang almost 3 years ago

  • Status changed from Fix Under Review to Duplicate

Also available in: Atom PDF