Actions
Feature #647
closedmon: refactor paxos interaction
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
We currently have a paxos instance per state machine, which is silly for a bunch of reasons. The big one is that a monitor might be up to date on, say, the osdmap, but out of date on the pgmap, which leads to weird availability states.
Also, when a monitor rejoins and is far behind, it tries to catch up immediately. We need a 'recovering' state during which the monitor can stream data that it is behind on, and then try to join the quorum.
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position set to 827
Updated by Sage Weil over 12 years ago
- Subject changed from refactor monitor code, paxos to mon: refactor paxos interaction
- Translation missing: en.field_position deleted (
828) - Translation missing: en.field_position set to 828
Updated by Sage Weil over 11 years ago
- Status changed from New to Duplicate
- Translation missing: en.field_position deleted (
1293) - Translation missing: en.field_position set to 1290
Actions