[ 
https://issues.apache.org/jira/browse/SOLR-17388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ella eln updated SOLR-17388:
----------------------------
    Description: 
* Requests to custom request handlers defined in {{solrconfig.xml}} are not 
federated by the coordinator. The coordinator logs do not show any activity for 
these requests, and the request ID (rid) is incorrectly assigned to a data 
replica rather than the coordinator.

 * {*}Expected Behavior{*}: Custom requests should be distributed by the 
coordinator, similar to {{/select}} requests.

 * {*}Current Behavior{*}: Only {{/select}} requests are properly federated by 
the coordinator. Custom handlers fail to be recognized, and logs for these 
requests are missing in the coordinator pod.

 * {*}Investigation{*}: The issue seems related to the code in 
{{CoordinatorV2HttpSolrCall}} (lines 43-49):


javaCopy code
{{protected SolrCore getCoreByCollection(String collectionName, boolean 
isPreferLeader) {    this.collectionName = collectionName;    SolrCore core = 
super.getCoreByCollection(collectionName, isPreferLeader);    if (core != null) 
return core;    if (!path.endsWith("/select")) return null;    return 
CoordinatorHttpSolrCall.getCore(factory, this, collectionName, isPreferLeader);
}}}
It appears that the code only federates requests if the path ends with 
{{{}/select{}}}.

 *  

 *  

> add coordinator support for costume RH by setting a list on solrconfig.xml
> --------------------------------------------------------------------------
>
>                 Key: SOLR-17388
>                 URL: https://issues.apache.org/jira/browse/SOLR-17388
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>    Affects Versions: 9.4, 9.7
>            Reporter: ella eln
>            Priority: Minor
>
> * Requests to custom request handlers defined in {{solrconfig.xml}} are not 
> federated by the coordinator. The coordinator logs do not show any activity 
> for these requests, and the request ID (rid) is incorrectly assigned to a 
> data replica rather than the coordinator.
>  * {*}Expected Behavior{*}: Custom requests should be distributed by the 
> coordinator, similar to {{/select}} requests.
>  * {*}Current Behavior{*}: Only {{/select}} requests are properly federated 
> by the coordinator. Custom handlers fail to be recognized, and logs for these 
> requests are missing in the coordinator pod.
>  * {*}Investigation{*}: The issue seems related to the code in 
> {{CoordinatorV2HttpSolrCall}} (lines 43-49):
> javaCopy code
> {{protected SolrCore getCoreByCollection(String collectionName, boolean 
> isPreferLeader) {    this.collectionName = collectionName;    SolrCore core = 
> super.getCoreByCollection(collectionName, isPreferLeader);    if (core != 
> null) return core;    if (!path.endsWith("/select")) return null;    return 
> CoordinatorHttpSolrCall.getCore(factory, this, collectionName, 
> isPreferLeader);
> }}}
> It appears that the code only federates requests if the path ends with 
> {{{}/select{}}}.
>  *  
>  *  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to