Bug #2031
paxos: failed assert (begin->last_committed == last_committed)
Status:
Can't reproduce
Priority:
Normal
Assignee:
-
Category:
Monitor
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Failed assert mon/Paxos.cc: 412: FAILED assert(begin->last_committed == last_committed)
I haven't spent much time looking into this, but lxo has reported seeing it intermittently. I was wondering if this could happen just by having the monitor fall behind due to slow disk syncs, but Sage doesn't think so.
History
#1 Updated by Sage Weil almost 12 years ago
oh.. maybe it was slurping, and crashed before it stashed. when it restarted it didn't go back into slurp, because the get_version()/last_committed was recent enough?
that slurp-or-no-slurp check should also verify that the stashed version is new enough?
#2 Updated by Greg Farnum almost 12 years ago
I think that could happen, so I'll check and fix it if so, but it's not what happened here.
#3 Updated by Sage Weil almost 12 years ago
oh, that was meant for #2032!
#4 Updated by Greg Farnum almost 12 years ago
Made a new bug for that issue anyway. #2037
#5 Updated by Sage Weil over 11 years ago
- Status changed from New to Can't reproduce