Feature #2651
mon: race calling tick() when doing slurping
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
Right now the monitor calls tick() on all the PaxosService implementations when it's doing slurping. This introduces a race, in the case that there is slurping going on which has changed the on-disk data without yet putting it back into a consistent state.
There is a quick fix in wip-tick-slurping-race, but we should come up with a stronger solution (integrate slurping into the Paxos state system, probably?) for master. (Or, hopefully, merge Joao's single-paxos stuff soon enough that we don't need to worry about it.)
Related issues
History
#1 Updated by Sage Weil over 11 years ago
- Status changed from New to Resolved
#2 Updated by Sage Weil over 11 years ago
- Status changed from Resolved to 12
oops, stronger fix, yes!
#3 Updated by Sage Weil about 11 years ago
- Tracker changed from Bug to Cleanup
making this a cleanup so that it stops confusing me :)
#4 Updated by Sage Weil over 10 years ago
- Tracker changed from Cleanup to Feature
- Status changed from 12 to Rejected
no more slurp.