- Issue created by @DamienMcKenna
- Assigned to DamienMcKenna
- πΊπΈUnited States DamienMcKenna NH, USA
Now that I've worked out the problem comes during cron execution I can start debugging it.
- π©πͺGermany mkalkbrenner π©πͺ
You need to check the Solr logs.
You can also increase the timeout on the server edit page in Drupal.
- π³π±Netherlands Steven Buteneers
I'm also experiencing this problem since updating from V4.2 to V4.3 together with updating from Drupal 9 to 10. It only appears on cron, regular indexing works like it's supposed to work.
- πΊπΈUnited States DamienMcKenna NH, USA
FWIW I'm seeing this on a Pantheon site, so I don't have access to the Solr logs.
- π³π±Netherlands Steven Buteneers
These are the logs generated in SOLR at the same time as the error occurs:
2023-10-30 13:30:03.086 INFO (qtp1548081008-23) [ x:shared] o.a.s.c.S.Request [shared] webapp=/solr path=/select params={q=*:*&json.facet={"maxVersion":"max(_version_)"}&json.nl=flat&omitHeader=false&fl=*,score&start=0&rows=1&wt=json} hits=6220 status=0 QTime=1
2023-10-30 13:30:11.020 INFO (qtp1548081008-20) [ x:shared] o.a.s.c.S.Request [shared] webapp=/solr path=/select params={q=*:*&json.facet={"maxVersion":"max(_version_)"}&json.nl=flat&omitHeader=false&fl=*,score&start=0&rows=1&wt=json} hits=6220 status=0 QTime=0
2023-10-30 13:30:25.445 INFO (qtp1548081008-22) [ x:shared] o.a.s.c.S.Request [shared] webapp=/solr path=/select params={q=*:*&json.facet={"maxVersion":"max(_version_)"}&json.nl=flat&omitHeader=false&fl=*,score&start=0&rows=1&wt=json} hits=6220 status=0 QTime=0
2023-10-30 13:30:25.519 INFO (qtp1548081008-22) [ x:drupal] o.a.s.c.S.Request [drupal] webapp=/solr path=/select params={q=*:*&json.facet={"maxVersion":"max(_version_)"}&json.nl=flat&omitHeader=false&fl=*,score&start=0&rows=1&wt=json} hits=36731 status=0 QTime=2
2023-10-30 13:30:25.606 INFO (qtp1548081008-22) [ x:drupal] o.a.s.h.c.SuggestComponent SuggestComponent prepare with : json.nl=flat&omitHeader=true&suggest.build=false&suggest.count=10&suggest.reload=false&suggest=true&suggest.buildAll=true&suggest.dictionary=und&wt=json&rid=-1664
2023-10-30 13:30:25.606 INFO (qtp1548081008-22) [ x:drupal] o.a.s.s.s.SolrSuggester SolrSuggester.build(und)
2023-10-30 13:30:30.712 INFO (qtp1548081008-22) [ x:drupal] o.a.s.s.s.SolrSuggester SolrSuggester.build(nl)
2023-10-30 13:30:35.476 INFO (qtp1548081008-22) [ x:drupal] o.a.s.h.c.SuggestComponent SuggestComponent process with : json.nl=flat&omitHeader=true&suggest.build=false&suggest.count=10&suggest.reload=false&suggest=true&suggest.buildAll=true&suggest.dictionary=und&wt=json&rid=-1664
2023-10-30 13:30:35.476 INFO (qtp1548081008-22) [ x:drupal] o.a.s.c.S.Request [drupal] webapp=/solr path=/suggest params={json.nl=flat&omitHeader=true&suggest.build=false&suggest.reload=false&suggest=true&suggest.buildAll=true&wt=json} status=0 QTime=9870 - π³π±Netherlands Steven Buteneers
Increasing the query and index timeouts from 5 to 10 seconds seems to "resolve" this
- π§πͺBelgium rp7
I can confirm that increasing the query timeout resolves the error.
Additionally, I think this cron-logic needs to be expanded to first see if the suggest request handler is enabled. You can disable it through the UI, but doing so will result in 404 Solr endpoint errors in the logs (when this cron is run).
- Assigned to mkalkbrenner
- π©πͺGermany mkalkbrenner π©πͺ
A provider like pantheon could block or disable the suggester request handler.
In this case you should also disable it via Search API Solr's UI.
This patch then "solves" the issue. - Status changed to Needs review
8 months ago 4:06pm 1 November 2023 - last update
8 months ago Patch Failed to Apply -
mkalkbrenner β
committed bd570cfd on 4.x
Issue #3392628 by mkalkbrenner: Don't build suggesters if disabled
-
mkalkbrenner β
committed bd570cfd on 4.x
- Status changed to Fixed
8 months ago 4:36pm 1 November 2023 - πΊπΈUnited States DamienMcKenna NH, USA
Thanks for working out a fix for that!
Automatically closed - issue fixed for 2 weeks with no activity.