[
https://issues.apache.org/jira/browse/SOLR-12770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-12770:
-------------------------------
Fix Version/s: 7.7
Thanks Tomas, works like a charm :) Guess this can be resolved now
> Make it possible to configure a shards whitelist for master/slave
> -----------------------------------------------------------------
>
> Key: SOLR-12770
> URL: https://issues.apache.org/jira/browse/SOLR-12770
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: search
> Reporter: Jan Høydahl
> Priority: Major
> Labels: masterSlave
> Fix For: 7.7
>
>
> For legacy master/slave clusters, there is no Zookeeper to keep track of all
> the nodes and shards in the cluster. So users manage the 'shards' parameter
> manually for distributed search. This issue will add the option of
> configuring a list of what shards can be requested.
> Users will then get an explicit error response if the request includes a
> shard which is not in the preconfigured whitelist, e.g. due to a typo. I
> think all shards logic is handled by HttpShardHandler already so the logic
> should fit nicely in that one class, configured in {{solr.xml}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
