Actions
Bug #2031
closedpaxos: failed assert (begin->last_committed == last_committed)
Status:
Can't reproduce
Priority:
Normal
Assignee:
-
Category:
Monitor
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
Severity:
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.
Updated by Sage Weil over 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?
Updated by Greg Farnum over 12 years ago
I think that could happen, so I'll check and fix it if so, but it's not what happened here.
Updated by Greg Farnum over 12 years ago
Made a new bug for that issue anyway. #2037
Updated by Sage Weil about 12 years ago
- Status changed from New to Can't reproduce
Actions