We are thinking about replacing MongoDB on Aerospike. We want to have different installation types with replication factor 1 and 2.
The question is about behavior of Aerospike when one node from the cluster goes down. And then come back in few minutes (15-40 for e. g.).
- What we will see on client side if we will request data stored on alive nodes?
- What we will see on client side if we will request data stored on dead node?
- How cluster will be reconfigured and how it will be restored after restoring node?
- What happened if we try to write data which should be stored on dead node?