We have a case of a Solr Cloud cluster with different kinds of nodes - some may have significant differences in hardware specs (50-100% more HD/RAM/CPU, etc). Ideally nodes with increased resources could take on more shard replicas.
It looks like the Collections API ( https://lucene.apache.org/solr/guide/6_6/collections-api.html) supports only even splitting of shards when using compositeId routing. The way to handle this right now looks to be running additional Solr instances on nodes with increased resources to balance the load (so if the machines are 1x, 1.5x, and 2x, run 2 instances, 3 instances, and 4 instances, respectively). Has anyone looked into other ways of handling this that don't require the additional Solr instance deployments? -Michael
