"Tim Fox on the Wiki page" wrote:
(Potentially in the future we will allow the configuration of multiple backup nodes for a single active node, but first we will concentrate on the simplest case.)
There is also the opposite case of a single backup node for multiple active nodes.
An user might want to keep only one backup for N nodes. (Say... 1 backup for every four active nodes).
Some thoughts I had:
- What should happen if you bring a "backup node" up, after the live node is running? - on that case how do we copy the state to the new node as new requests are coming? If we support that, is it possible to do that without requiring a valve and lock the server for some time?
Yes, that's difficult.
I'm going to concentrate on getting the simples case working first.