Torsten Bøgh Köster created SOLR-17334:
------------------------------------------
Summary: Minor bugs in Solr dedicated coordinator mode
Key: SOLR-17334
URL: https://issues.apache.org/jira/browse/SOLR-17334
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Components: SolrCloud
Affects Versions: 9.6
Reporter: Torsten Bøgh Köster
We recently put dedicated Solr coordinator nodes into production
and stumbled upon some minor bugs/improvements:
- The Solr root resource cannot be requested on a coordinator node
- Coordinator requests are enabled for the {{/select}} handler only
- From outside proxied and coordinator requests cannot be distinguished
h3. Solr root resource
We adopted a general fix from the {{HttpSolrCall}} to check whether the
given {{collectionName}} is {{{}null{}}}. This fixes requesting the root
resource
(and maybe other similar requests)
h3. {{/select}} handler only
Coordinator requests are limited to the {{/select}} handler. In our environment
we make heavy usage of pre-configured Solr handlers. We could not find any
reason to limit coordinator calls to the {{/select}} handler and removed the
limitation.
h3. Coordinator requests cannot be identified by Solr response
With any Solr response you cannot distinguish coordinator from proxied
(or regular) requests. While this is great for consistency it makes testing
extra hard. We added an extra Solr header field with the coordinator node
name called {{requestCoordinatorNode}} when debug is enabled.
This eases testing and debugging a lot.
A Pull Request is in the making!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
