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-
n there's a replica count
> autoscaling policy)
>
>
>
> Rajeswari posted a separate reply to this thread that brought me to another
> discovery.
>
> https://lucene.472066.n3.nabble.com/Re-CAUTION-Re-Solr-7-7-restore-issue-tp4450714.html
>
> In it, they referenc
oscaling policy)
Rajeswari posted a separate reply to this thread that brought me to another
discovery.
https://lucene.472066.n3.nabble.com/Re-CAUTION-Re-Solr-7-7-restore-issue-tp4450714.html
In it, they reference the legacy rule based replica placement documentation:
https://lucene.apache.org/solr
I also ran into this while researching cluster policies. Solr 7.6
Except same situation: introduce a rule to control placement of
collections. Backup. Delete. Restore. Solr complains it can't do it.
I don't need them just yet, so I stopped there, but reading this is quite
disturbing.
Does deleti
It looks like the rule created before was wrong.
From the solr documentation below
https://lucene.apache.org/solr/guide/7_6/rule-based-replica-placement.html
For a given shard, keep less than 2 replicas on any node
For this rule, we use the shard condition to define any shard, the replica
condit
I am also facing the same issue. With Solr 7.6 restore fails with below rule.
Would like to place one replica per node by below rule
with the rule to place one replica per node
"set-cluster-policy": [{
"replica": "<2",
"shard": "#EACH",
"node": "#ANY"
}]
Without the
I have a 4 node cluster. My goal is to have 2 shards with two replicas
each and only allowing 1 core on each node. I have a cluster policy set to:
[{"replica":"2", "shard": "#EACH", "collection":"test",
"port":"8983"},{"cores":"1", "node":"#ANY"}]
I then manually create a collection with:
name
Hi,
Just need to check the following.
Currently building a test environment with solrcloud and 3 nodes After loading
some data into solr I did the following:
1. create a backup using the replication handler like
http://localhost:8983/solr/ [SHARDNAME]
/replication?command=backup&location=/da
