My scenario is: - 60 GB collection - 2 shards of ~30GB - Each shard having 2 replicas so I have a backup - So I have 4 nodes with each node holding a single core
My goal is to have autoscaling handle when I lose a node. So upon loss of a node the nodeLost event deletes the node. Then when I add back in another node I want it to replace the node I lost keeping each shard with 2 replicas. The problem is that I can't find a policy that keeps 2 replicas per shard because when the nodeAdded event fires it wants to add a 3rd replica to the shard that already has 2 replicas. I can't seem to get it to add the replica to the shard that is left with the single replica. Any suggestions on a policy to keep this balanced? Mark
