Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1. Allow all masters to remain active, pushing all state into ZK so it's shared between them. Clients retain the list of all possible masters and pick one at random to connect to. Deal with E2E ACKs by pushing them into ZK.
1. Have masters go through an election process, push all state into ZK so it's shared between them in the case of failure. Clients no longer contain the list of masters and instead contain the ZK quorum node list. The current master is fetched from ZK. Deal with E2E ACKs by pushing them into ZK so in the case of master failover, no ACKs are lost.
1. Have masters go through an election process, push all state into ZK so it's shared between them in the case of failure. Clients no longer contain the list of masters and instead contain the ZK quorum node list. The current master is fetched from ZK. Deal with E2E ACKs by simply letting them expire and be retransmitted in the case of master failover.