Hi Andrzej ,

I have put the JSONs produced by "save" commands below:

autoscalingState.json - https://pastebin.com/CrR0TdLf
clusterState.json - https://pastebin.com/zxuYAMux
nodeState.json https://pastebin.com/hxqjVUfV
statistics.json https://pastebin.com/Jkaw8Y3j

The simulate command is:
/opt/solr-8.3.0/bin/solr autoscaling -a policy2.json -simulate  -zkHost 
rexcloud-swoods-zookeeper-headless:2181

Policy2 can be found here:
https://pastebin.com/VriJ27DE

Setup:
12 nodes on Kubernetes. 6 for TLOG and 6 for Pull. The simulation is run on one 
of nodes inside Kubernetes because it needs the zookeeper inside the Kubernetes.

Thanks!

Li


On 12/15/19, 5:13 PM, "Andrzej Białecki" <a...@getopt.org> wrote:

    Could you please provide the exact command-line? It would also help if you 
could provide an autoscaling snapshot of the cluster (bin/solr autoscaling 
-save <snapshotDir>) or at least 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 <li_...@comcast.com> wrote:
    >
    > 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.ExecutionException: org.apache.solr.common.SolrException: 
org.apache.solr.common.SolrException: Could not find collection : 
entity/shards",
    >          "suggestion":{
    >            "type":"repair",
    >            "operation":{
    >              "method":"POST",
    >              "path":"/c/entity/shards",
    >              "command":{"add-replica":{
    >                  "shard":"shard2",
    >                  "node":"my_node:8983_solr",
    >                  "type":"TLOG"}}}},
    >          "replicaInfo":null}}},
    >
    > Does anyone know how to fix this? Is this a bug?
    >
    > Thanks!
    >
    > Li


Reply via email to