lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-13248) Autoscaling based replica placement is broken out of the box
Date Tue, 19 Feb 2019 01:21:00 GMT


ASF subversion and git services commented on SOLR-13248:

Commit 884a70d0b7bb009e775702db0b3fe7c509b9ac02 in lucene-solr's branch refs/heads/branch_8_0
from Shalin Shekhar Mangar
[;h=884a70d ]

SOLR-13248: Adding upgrade notes which explain the problem and the mitigation as well as steps
to revert to the old behavior

(cherry picked from commit 97875af3f93477f48e4ead1979b2f36797106e06)

> Autoscaling based replica placement is broken out of the box
> ------------------------------------------------------------
>                 Key: SOLR-13248
>                 URL:
>             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-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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message