[jira] [Updated] (SOLR-11619) V2 API doesn't route to other nodes when the local node can't satisfy the request

["David Smiley (JIRA)" <ji...@apache.org>]

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

David Smiley updated SOLR-11619:
--------------------------------
    Attachment: SOLR_11619_V2_action_REMOTEQUERY_bug.patch

Attached is a patch that fixes the problem.  I decided to move the "path" manipulation out of extractRemotePath so that we have the nice property that it's only ever updated from init() without exceptions... plus it makes it easier to call by V2.

There is no explicit test admittedly :-/   except that SOLR-11542 triggers this bug and it now works.

[~noble.paul] could you please take a look?

> V2 API doesn't route to other nodes when the local node can't satisfy the request
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-11619
>                 URL: https://issues.apache.org/jira/browse/SOLR-11619
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: David Smiley
>            Assignee: David Smiley
>             Fix For: 7.2
>
>         Attachments: SOLR_11619_V2_action_REMOTEQUERY_bug.patch
>
>
> There is some code in V2HttpCall to handle the case when the local node doesn't have a core to satisfy the request.  But AFAICT it's broken, which I discovered while writing tests in SOLR-11299.  The code will trigger an NPE since it seems to get to an action state of PROCESS yet there is no core or config.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org