lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <>
Subject [jira] [Commented] (SOLR-12868) Request forwarding for v2 API is broken
Date Thu, 17 Jan 2019 00:45:00 GMT


Cassandra Targett commented on SOLR-12868:

[~noble.paul], here's *another* issue that appears in CHANGES.txt for 7.6 but isn't marked
as resolved. Can it be resolved?

It seems to happen frequently that we find issues that should have been resolved months ago.
Any way you could modify the way you work with issues so these are resolved closer to the
time of your commits, like the rest of us do?

> Request forwarding for v2 API is broken
> ---------------------------------------
>                 Key: SOLR-12868
>                 URL:
>             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: 7.6, 8.0
> 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 {{}}
and {{/c/collection1/abccdef}} is forwarded as {{}}
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message