You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2017/11/08 16:58:00 UTC
[jira] [Resolved] (SOLR-11619) V2 API doesn't route to other nodes
when the local node can't satisfy the request
[ https://issues.apache.org/jira/browse/SOLR-11619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley resolved SOLR-11619.
---------------------------------
Resolution: Fixed
> 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