[
https://issues.apache.org/jira/browse/SOLR-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-6695.
----------------------------------
Resolution: Invalid
There has never been an automatic reload of the collections based on manually
uploading changed configurations.
You can reload the _collection_ with a single command though.
This is orthogonal to eliminating the maxBooleanClauses in the first place.
Ran across this when looking for something else, closing it seems in order.
> Change in solrconfig.xml for maxBooleanClauses in SolrCloud is not recognized
> -----------------------------------------------------------------------------
>
> Key: SOLR-6695
> URL: https://issues.apache.org/jira/browse/SOLR-6695
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.9, 4.10, 4.10.2
> Reporter: Robert Parker
> Priority: Minor
>
> Under Solr 4.10.2 in solrcloud configuration, if I upload a change to
> solrconfig.xml to zookeeper that raises maxBooleanClauses from 1024 to 2048
> and then reload the collection, the cores do not recongnize a new value for
> maxBooleanClauses unlike other changes to schema.xml and solrconfig.xml. I
> have to bounce Solr on each node before queries will honor the new value for
> maxBooleanClauses. This seems like unintentional behavior. I should be able
> to make any change to schema.xml and solrconfig.xml, then upload those to
> zookeeper and have each node in the cluster instantly honor all new values
> after a core/collection reload.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
