fpaxos / fpaxos-lib Goto Github PK

Is replica 0 hardcoded as the proposer?

We tried running an experiment with 3 nodes on 3 VMs changing paxos.conf the same way as was done in fpaxos-test:

q1 = 2
q2 = 1
g1 = 2
g2 = 1

learner-catch-up no

lmdb-env-path /tmp/acceptor

The replicas were started in the following order: 0, 1, 2
A client was started on the same server as replica 0
When the replica 0 was killed replica 1 and 2 were not able to elect a new leader, although they should have the size of quorum 1 is 2. Starting replica 0 up again and the client was still not able to connect. Only after also restarting the client we were able to send values again.

Another test we did was starting the replicas in the order 1, 0, 2.
A client was started on the same server as replica 1
Killing replica 0 and the client couldn't send any values anymore.
Doing the same thing and killing replica 1 also resulted in 0 values/sec

There's no logging to display who is elected leader, but it seems that replica 0 always is elected leader. Is that correct?

If there is no current proposer VMs that are running replicas becomes totally unresponsive in less than a minute. Couldn't even kill the process. Had to soft reboot the VM.