[
https://issues.apache.org/jira/browse/SOLR-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771472#comment-16771472
]
ASF subversion and git services commented on SOLR-13248:
--------------------------------------------------------
Commit 521701dd9cf8ff20a02bb25f9512f17247840eed in lucene-solr's branch
refs/heads/branch_8_0 from Shalin Shekhar Mangar
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=521701d ]
SOLR-13248: Autoscaling based replica placement is broken out of the box.
Solr 7.5 enabled autoscaling based replica placement by default but in the
absence of default cluster policies, autoscaling can place more than 1 replica
of the same shard on the same node. Also, the maxShardsPerNode and
createNodeSet was not respected. Due to these reasons, this issue reverts the
default replica placement policy to the 'legacy' assignment policy that was the
default until Solr 7.4.
Cherry-picked from commit 7ede4e2b
> 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.6, 7.7
> Reporter: Shalin Shekhar Mangar
> Priority: Blocker
> Fix For: 8.0
>
> Attachments: SOLR-13248-withDefaultCollectionProp.patch,
> SOLR-13248.patch, SOLR-13248.patch, SOLR-13248.patch
>
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
