In a bare-metal deployment, the indexer keeps three copies of data on three physical nodes for data availability. Even if 2 node goes down, data will be available on the third node. But, in the case of microservices, how do the containers manage the data copies? There can be multiple indexer-containers running on the same physical node and three copies of data might sit on the same physical node. If such node goes down we might lose the data. Now, is there a way to keep three copies of data on the different physical nodes in a container-based deployment?
