Unfortunately, upon further testing, my above suggestion about using only the
set-policy does not actually solve the issue.
The reason my testing above worked with restore was only because I left out
the problematic set-cluster-policy autoscaling rule for replica count. And
the truth is that resto
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-
Would anyone be able to confirm that this is indeed a Solr bug between
restore and autoscaling?
I have done some local testing and found the following patterns and
discoveries.
When using a replica count autoscaling policy {"replica": "<2","shard":
"#EACH","node": "#ANY"}, it breaks Solr restore
