[
https://issues.apache.org/jira/browse/SOLR-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845149#comment-16845149
]
Cassandra Targett commented on SOLR-12868:
------------------------------------------
[~noble.paul] - please see my earlier comment about this appearing in 7.6
CHANGES. Is it resolved? Since the RM process automatically bumps versions,
this now appears as though it's slated to be in 8.2, although from what I can
tell - but can't be sure - it seems this was fixed in 7.6.
> Request forwarding for v2 API is broken
> ---------------------------------------
>
> Key: SOLR-12868
> URL: https://issues.apache.org/jira/browse/SOLR-12868
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud, v2 API
> Reporter: Shalin Shekhar Mangar
> Assignee: Noble Paul
> Priority: Major
> Fix For: master (9.0), 8.2
>
>
> I was working with Noble Paul to investigate test failures seen in SOLR-12806
> where we found this issue. Due to a bug, replicas of a collection weren't
> spread evenly so there were some nodes which did not have any replicas at
> all. In such cases, when a v2 API call hits an empty node, it is not
> forwarded to the right path on the remote node causing test failures.
> e.g. a call to {{/c/collection/_introspect}} is forwarded as
> {{http://127.0.0.1:63326/solr/collection1/_introspect?method=POST&wt=javabin&version=2&command=XXXX}}
> and {{/c/collection1/abccdef}} is forwarded as
> {{http://127.0.0.1:63326/solr/collection1/abccdef}}
> In summary, a remote query for v2 API from an empty node is converted to a v1
> style call which may not be a valid path. We should forward v2 API calls
> as-is without changing the paths.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
