SOLR error: too many boolean clauses

70 views
Skip to first unread message

Sean Carte

unread,
Feb 17, 2020, 7:34:03 AM2/17/20
to DSpace Technical Support
I have a dspace 6.3 instance running on Ubuntu 18.04.3. When a user who belongs to two groups that are authorised to add to and edit all collections, a very long error is generated, ending with:

...
OR l9d9b96b2-ae23-40ea-9e98-46a8537ac4b5 OR lf94b27dc-2c22-476c-a012-72f36b50d521 OR lfd7afb4f-8a09-4412-8044-2acbe584fa76)': too many boolean clauses
        at org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:552)
        at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
        at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
        at org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91)
        at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:310)
        at org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:1610)
        ... 364 more

I've attached the solr.log containing the full error.

Removing the user from either of the groups resolves the problem. Also, if the user is an administrator the problem does not occur.

The problem occurs irrespective of the UI.

I downloaded a fresh copy of DSpace and updated the existing installation with it, but that didn't help. I deleted the /dspace directory and did a fresh installation, then restored the database; the problem persists.

But, I copied the database to a laptop (running the same versions of all software) and the problem went away.

If the problem doesn't exist in the database, where could it be? Does anybody have any ideas?

DSpace version:  6.3
  SCM revision:  813800ce1736ec503fdcfbee4d86de836788f87c
    SCM branch:  UNKNOWN
            OS:  Linux(amd64) version 4.15.0-74-generic
     Discovery:  enabled.
           JRE:  Private Build version 1.8.0_242
   Ant version:  Apache Ant(TM) version 1.10.5 compiled on March 28 2019
 Maven version:  3.3.9
   DSpace home:  /dspace
Tomcat 8
PostgreSQL 10

/etc/default/tomcat8: JAVA_OPTS="-Djava.awt.headless=true -Xmx8192m -Xms4096m -XX:+UseConcMarkSweepGC -Dfile.encoding=UTF-8 -XX:MaxPermSize=512m"
--

solr.log.20200217

Claudia Jürgen

unread,
Feb 17, 2020, 10:44:30 AM2/17/20
to dspac...@googlegroups.com
Hello Sean,

this might be related to the Access Rights Awareness
see
https://wiki.lyrasis.org/display/DSPACE/TechnicalFaq#TechnicalFAQ-I'mgetting%22SolrException:BadRequest%22followedbyalongqueryora%22tooManyClauses%22Exception

Hope this helps

Claudia Jürgen
--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia...@tu-dortmund.de
www.ub.tu-dortmund.de


Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax.

Sean Carte

unread,
Feb 18, 2020, 12:58:51 AM2/18/20
to Claudia Jürgen, DSpace Technical Support
Thank you, Claudia!

Disabling the Access Rights Awareness feature does appear to resolve the issue.

I did try increasing the maxBooleanClauses setting first, but it looks like this may get set elsewhere, so I found all the solrconfig.xml and increased it in all of them. That also resolves the issue.

--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/018898d5-6a6c-6225-73df-6c69f6f5fc16%40tu-dortmund.de.


--

Alan Orth

unread,
Feb 19, 2020, 5:49:44 AM2/19/20
to Sean Carte, Claudia Jürgen, DSpace Technical Support
Dear list,

We have many users, collections, and groups and have run into both problems mentioned here. Over the last few years we hаve incremented both the Tomcat header size as well as the Solr max boolean clauses. I had no idea about this access rights awareness feature! I suspect turning this off will also give our Solr server a little bit of a break. :)

Cheers!



--
Reply all
Reply to author
Forward
0 new messages