All nodes detected as replicas

[quintonparker]

See sheet https://docs.google.com/spreadsheets/d/1sx-wKfHocVInDt3VnxQc4BLxWzPkKqtJD0og48-ob1A/edit?usp=sharing

For prod database, node prod-002 is clearly the master as judged by metrics such as cache hits etc. and importantly replication lag is 0 which is the giveaway

This in turn throws off redis2re which then proceeds to size this database with 2x micro shards when instead it should be 4x HT shards

[thomasefthymiou78]

Usually this events makes the script fail and the solution is to manually define the master node and run it again. Looks like we can use some of this information to automatically fix the issue, but still not sure if we should.