Thanks Hoss,
Yes, i was making the change in solr.xml in wrong directory earlier.
Also as you said:
: You need to update EVERY solrconfig.xml that the JVM is loading for this
to
: actually work.
that has not been true for a while, see SOLR-13336 / SOLR-10921 ...
I validated this and it's working as expected. We don't need to update
every solrconfig.xml.
The value mentioned in solr.xml is global and if maxBooleanClauses for any
collection in solrconfig.xml exceeds the limit specified in solr.xml then
we get the exception.
Thanks for replying.
On Wed, Jan 6, 2021 at 10:57 PM dinesh naik <dineshkumarn...@gmail.com>
wrote:
> Thanks Shawn,
>
> This entry <int name="maxBooleanClauses">${sol
> r.max.booleanClauses:2048}</int> in solr.xml was introduced only in solr
> 8.x version and were not present in 7.6 version.
>
> We have this in solrconfig.xml in 8.4.1 version.
> <!-- Maximum number of clauses allowed when parsing a boolean query
> string. This limit only impacts boolean queries specified by a user as part
> of a query string, and provides per-collection controls on how complex user
> specified boolean queries can be. Query strings that specify more clauses
> then this will result in an error. If this per-collection limit is greater
> then the global `maxBooleanClauses` limit specified in `solr.xml`, it will
> have no effect, as that setting also limits the size of user specified
> boolean queries. --> <maxBooleanClauses>${solr.max.booleanClauses:2048}</
> maxBooleanClauses>
> i was updating the solr.xml in the installation directory and not the
> installed data directory, hence the change was not reflecting.
> After updating the correct solr.xml and restarting the Solr nodes the new
> value is working as expected.
>
> On Wed, Jan 6, 2021 at 10:34 PM Chris Hostetter <hossman_luc...@fucit.org>
> wrote:
>
>>
>> : You need to update EVERY solrconfig.xml that the JVM is loading for
>> this to
>> : actually work.
>>
>> that has not been true for a while, see SOLR-13336 / SOLR-10921 ...
>>
>> : > 2. updated solr.xml :
>> : > <int name="maxBooleanClauses">${solr.max.booleanClauses:2048}</int>
>> :
>> : I don't think it's currently possible to set the value with solr.xml.
>>
>> Not only is it possible, it's neccessary -- the value in solr.xml acts as
>> a hard upper limit (and affects all queries, even internally expanded
>> queries) on the "soft limit" in solrconfig.xml (that only affects
>> explicitly supplied boolean queries from users)
>>
>> As to the original question...
>>
>> > 2021-01-05 14:03:59.603 WARN (qtp1545077099-27)
>> x:col1_shard1_replica_n3
>> > o.a.s.c.SolrConfig solrconfig.xml: <maxBooleanClauses> of 2048 is
>> greater
>> > than global limit of 1024 and will have no effect
>>
>> I attempted to reproduce this with 8.4.1 and did not see the probem you
>> are describing.
>>
>> Are you 100% certain you are updating the correct solr.xml file? If you
>> add some non-xml giberish to the solr.xml you are editing does the solr
>> node fail to start up?
>>
>> Remember that when using SolrCloud, solr will try to load solr.xml from
>> zk
>> first, and only look on local disk if it can't be found in ZK ... look
>> for
>> log messages like "solr.xml found in ZooKeeper. Loading..." vs "Loading
>> solr.xml from SolrHome (not found in ZooKeeper)"
>>
>>
>>
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>
>
> --
> Best Regards,
> Dinesh Naik
>
--
Best Regards,
Dinesh Naik
