THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- upon receipt of <activate-config, M’, leader(M’)> in configuration M’
- start serving operations in M’
- the first operation should clean up any incomplete reconfig request from M’
- send <activate-config-ack> to leader(M) and to leader(M')
- A non-leader server can start processing client operations in M’
- start serving operations in M’
- upon receipt of <activate-config, M’, leader(M’)> from leader(M) and <activate-config-ack> from quorum of members(M'), leader(M') does the following:
- commit all operations sent by leader(M) to members(M') during phase-1.
- start processing client operations in M’
- Make sure that all incomplete reconfig requests potentially unnoticed by the reconfiguration will never be applied
- property of ZAB ?
- upon receipt of <retire, version(M)>
- garbage-collect M
...