Before you do that, there’s not a lot of reason to. The actual extra load on the leaders is relatively minimal. Besides, the leadership will change depending on what replicas comes up first.
But if you insist, the collections API BALANCESHARDUNIQUE and REBALANCELEADERS will do this. These commands were put in for a case where there were 100s of leaders that were on the same node, I don’t think 24 is going to load up your machine. BTW, the only time being a leader actually does add load is when indexing, so unless you’re indexing at a very high rate there won’t be much work at all. This assumes NRT replicas. I don’t actually know if those collections API commands work with TLOG replicas, they were put in before TLOG replicase were invented. Best, Erick > On Aug 3, 2020, at 2:46 PM, Jae Joo <jaejo...@gmail.com> wrote: > > I have a cluster with 8 nodes for 24 shards with replicaFactor=3 and have > only 4 nodes have the leader replicas. > Is there any way to redistribute the lead nodes to cross of all 8 nodes? > > Thanks,
