[
https://issues.apache.org/jira/browse/SOLR-12847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161571#comment-17161571
]
Gus Heck commented on SOLR-12847:
---------------------------------
FWIW when I was investigating and fixing the MOVEREPLICA docs I found that
maxShardsPerNode is advisory only once the collection is created and in not a
hard limit. If destination node is specified in ADDREPLICA it will force
placement above the limit and move replica always issues its add with a
specified value for the node. Thus, MOVEREPLICA entirely ignores
maxShardsPerNode.
> Cut over implementation of maxShardsPerNode to a collection policy
> ------------------------------------------------------------------
>
> Key: SOLR-12847
> URL: https://issues.apache.org/jira/browse/SOLR-12847
> Project: Solr
> Issue Type: Bug
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: master (9.0)
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We've back and forth over handling maxShardsPerNode with autoscaling policies
> (see SOLR-11005 for history). Now that we've reimplemented support for
> creating collections with maxShardsPerNode when autoscaling policy is
> enabled, we should re-look at how it is implemented.
> I propose that we fold maxShardsPerNode (if specified) to a collection level
> policy that overrides the corresponding default in cluster policy (see
> SOLR-12845). We'll need to ensure that if maxShardsPerNode is specified then
> the user sees neither violations nor corresponding suggestions because of the
> default cluster policy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
