Hi!
I have some custom cache set up in solrconfig XML for a solr cloud cluster in
Kubernetes. Each node has Kubernetes persistence set up. After I execute a
“delete pod” command to restart a node it goes into Replication Recovery
successfully but my custom cache’s warm() method never gets calle
Thank you for creating the JIRA! Will follow
On 12/19/19, 11:09 AM, "Andrzej Białecki" wrote:
Hi,
Thanks for the data. I see the problem now - it’s a bug in the simulator. I
filed a Jira issue to track and fix it: SOLR-14122.
> On 16 Dec 2019, at 19:13, C
ou’re only allowed to use #ANY or a single specific node name (with optional
“!" NOT operand), or a JSON array containing node names to indicate the IN
operand.
The Ref Guide indeed is not very clear on that…
> On 17 Dec 2019, at 21:20, Cao, Li wrote:
>
> Hi!
Hi!
I am trying to add a cluster policy to a freshly built 8.3.0 cluster (no
collection added). I got this error when adding such a cluster policy
{
"set-cluster-policy":[{"cores":"<3","nodeset":{"sysprop.rex.node.type":"tlog"}}]}
Basically I want to limit the number of cores for certain machi
east the autoscaling diagnostic info.
(Please note that the mailing list removes all attachments, so just provide
a link to the snapshot).
> On 15 Dec 2019, at 18:42, Cao, Li wrote:
>
> Hi!
>
> I am using solr 8.3.0 in cloud mode. I have collection level autoscal
Hi!
I am using solr 8.3.0 in cloud mode. I have collection level autoscaling policy
and the collection name is “entity”. But when I run autoscaling simulation all
the steps failed with this message:
"error":{
"exception":"java.io.IOException:
java.util.concurrent.ExecutionExc
