Shalin Shekhar Mangar created SOLR-12023:
--------------------------------------------
Summary: Autoscaling policy engine shuffles replicas needlessly
and can also suggest nonexistent replicas to be moved
Key: SOLR-12023
URL: https://issues.apache.org/jira/browse/SOLR-12023
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: AutoScaling, SolrCloud
Reporter: Shalin Shekhar Mangar
Fix For: master (8.0), 7.3
A test that I wrote in SOLR-11066 found the following problem:
Cluster: 2 nodes
Collection: 1 shard, 3 replicas, maxShardsPerNode=5
No autoscaling policy or preference applied
When the trigger runs, the computed plan needlessly shuffles all three replicas
and then proceeds to return suggestions with only numbers as core names. These
cores do not exist. I found that these numbers are generated internally by the
framework as placeholders for moved cores for further calculations. They should
never ever be suggested to the users.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
