[ https://issues.apache.org/jira/browse/SOLR-11619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243470#comment-16243470 ]
Shalin Shekhar Mangar commented on SOLR-11619: ---------------------------------------------- This sounds very similar to SOLR-11130 which was supposed to have been fixed for 7.0. > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org