Project

General

Profile

Actions
Copy link

Bug #14075

closed

OSD: wrongly placed assert during handle_pg_peering_evt.

Added by xie xingguo over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
High
Assignee:
Samuel Just
Category:
-
Target version:
-
% Done:

0%

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

Description

"assert(service.splitting(pgid))" will definitely fire if PG is currently unavailable and _try_resurrect_pg returns RES_PARENT.

Actions
Copy link
 #1

Updated by Samuel Just over 8 years ago

  • Assignee set to Samuel Just

I don't understand. Can you elaborate on the incorrect case?

Actions
Copy link
 #2

Updated by Samuel Just about 8 years ago

  • Status changed from New to Resolved

I don't think so. That assert is there because RES_PARENT can only happen if the pg we are resurrecting is going to split into the pg we actually want to create. See _create_lock_pg and the call to service.init_splits_between. Reopen if I'm missing something!

Actions
Copy link

Also available in: Atom PDF