You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Parker (JIRA)" <ji...@apache.org> on 2014/11/03 22:31:33 UTC
[jira] [Created] (SOLR-6695) Change in solrconfig.xml for
maxBooleanClauses in SolrCloud is not recognized
Robert Parker created SOLR-6695:
-----------------------------------
Summary: 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.10.2, 4.10, 4.9
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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org