Professor Murat Demirbas has a (short) post looking at the Paxos serialization, comparing it with serializability and then introducing the notion of proactive serialization:
In fact Paxos serialization is overkill, it is too strong. Paxos will
serialize operations in a total order, which is not necessarily needed for
sequential consistency. Today in many applications where knowing the total
order and replicated-logging of that order is not important, Paxos is still
Indeed the post doesn’t offer too many details about proactive serialization, but while thinking about it here were my first questions:
- what would be the behavior of the system for the cases where the prediction for locks is incorrect? Somehow the behavior of the system would need to account for both false positives and false negatives.
- would a system using proactive serialization still need a coordinator? A master-service? (nb: if I’m reading the post correctly, it seems that the system would rely on a lock-service master)
- if there isn’t a coordinator who would make sure the locks are released when failures occur?
Original title and link: Paxos serialization, serializability, and proactive serialization ( ©myNoSQL)