Feature #14033
open
#14032 implementation should satisfy this one
Actually, it doesn't. http://tracker.ceph.com/issues/14032 covers the primary making a decision about which log is authoritative. During activation, the peers receive the authoritative log and need to atomically rollback/forward to last_update. We already do this with rollback, this feature would include extending that mechanism to cover rollforward as well.
- Assignee set to Samuel Just
- Status changed from New to In Progress
- % Done changed from 0 to 90
- Status changed from In Progress to 7
- Status changed from 7 to Fix Under Review
Also available in: Atom
PDF