I am now noticing a difference when using set-policy instead of set-cluster-policy. I'm still testing it to make sure, but just wanted to report early that the bug may rely on the type of policy being put in place.
So if you run into this issue when using set-cluster-policy, consider trying a set-policy like below: curl -X POST "http://localhost:8983/solr/admin/autoscaling"; --data-binary \ '{"set-policy": {"policy1": [{"replica": "<2", "shard": "#EACH", "node": "#ANY"}]}}' Whether this is a bug or not, I'll leave to the Solr devs. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
