[
https://issues.apache.org/jira/browse/SOLR-11239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128677#comment-16128677
]
ASF subversion and git services commented on SOLR-11239:
--------------------------------------------------------
Commit 057f9a63f62901fea73e03021ab319c26354b508 in lucene-solr's branch
refs/heads/branch_7_0 from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=057f9a6 ]
SOLR-11239: A special value of -1 can be specified for 'maxShardsPerNode' to
denote that there is no limit. The bin/solr script send maxShardsPerNode=-1
when creating collections. The use of maxShardsPerNode is not supported when a
cluster policy is in effect or when a collection specific policy is specified
during collection creation
(cherry picked from commit 7a576ffa1b1f4b9632ff2767686fe203949c2aaf)
# Conflicts:
# solr/CHANGES.txt
(cherry picked from commit 73015a6)
> Deprecate maxSHardsPerNode when autoscaling policies are used
> -------------------------------------------------------------
>
> Key: SOLR-11239
> URL: https://issues.apache.org/jira/browse/SOLR-11239
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.0
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Blocker
> Attachments: SOLR-11239.patch, SOLR-11239.patch
>
>
> We have found out that {{maxShardPerNode}} is not compatible with the new
> auto scaling policies. So we need to deprecate that parameter when the
> autoscaling policies are used.
> the {{bin/solr}} script passes that parameter all the time irrespective of
> whether the user needs it or not.
> We need to fix it for 7.0 itself
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
