lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <>
Subject [jira] [Updated] (SOLR-12868) Request forwarding for v2 API is broken
Date Tue, 21 May 2019 19:29:00 GMT


Noble Paul updated SOLR-12868:
    Fix Version/s:     (was: 8.2)
                       (was: master (9.0))

> 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
> 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