为什么将多人票称为多人票？

这是关于算法的多次轮次，以便以最少的消息传递来同意稳定领导者的顺序请求。最初，没有公认的领导者，您必须运行至少一轮基本Paxos，候选人领导者会发送准备请求（使用论文 Paxos变得简单）。多数人的积极回应证实它是领导者。然后，它发送该回合的接受消息，如果您获得大多数接受确认，则该消息成功终止。它可以立即转移到舞动模式，在此模式中，当它听到对先前接受请求的大多数确认时，会发送连续的接受消息，而不必立即从准备请求开始。这是非常高效的，因为它需要最少的消息数量，但仅在稳定领导者进行的多次回合中才发生。领导者崩溃可能会导致中断，否则网络故障会导致追随者在原本健康的领导者上超时。然后，它将发出自己的准备请求作为领导挑战，通过基本Paxos规则解决。一旦获得稳定的领导者，它便可以升级到多Paxos舞动模式。

It's about multiple rounds of the algorithm to agree sequential requests from a stable leader with minimal messaging. Initially with no recognised leader you must run at least one round of basic Paxos where a candidate leader sends a prepare request (using the terminology of the paper Paxos Made Simple). Positive responses from a majority confirm it as leader. It then sends accept messages for that round which terminates successfully if you get a majority of accept acknowledgements. Rather than start again with prepare requests it can move immediately to a galloping mode where it sends successive accept messages when it hears a majority of acknowledgments for the previous accept request. This is highly efficient as it needs the minimal number of messages but it only occurs for multiple rounds from a stable leader. This may be interrupted by the leader crashing else a network failure which causes a follower to timeout on an otherwise healthy leader. It will then issue its own prepare request as a leadership challenge which is resolved via basic Paxos rules. As soon as you get a stable leader it can upgrade to multi-Paxos galloping mode.