You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2019/02/14 12:37:00 UTC
[jira] [Created] (SOLR-13248) Autoscaling based replica placement
is broken out of the box
Shalin Shekhar Mangar created SOLR-13248:
--------------------------------------------
Summary: Autoscaling based replica placement is broken out of the box
Key: SOLR-13248
URL: https://issues.apache.org/jira/browse/SOLR-13248
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: AutoScaling
Affects Versions: 7.7, 7.6
Reporter: Shalin Shekhar Mangar
Fix For: 8.0
SOLR-12739 made autoscaling as the default replica placement strategy. However in the absence of SOLR-12845, replicas can be placed without any regards for maxShardsPerNode causing multiple replicas of the same shard to be placed on the same node together. Also it was reported in SOLR-13247 that createNodeSet is not being respected as well.
SOLR-13159 was an early signal of the problem but it was not reproducible and there was a DNS problem in the cluster too so the root cause was not clear then.
I am creating this blocker issue because as it stands today, we cannot guarantee the layout of new collections. At a minimum, we should revert to using the legacy replica assignment policy or add default policies with SOLR-12845 and have createNodeSet work. Related but not mandatory would be to fix SOLR-12847 as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org