You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/01/29 16:49:00 UTC

[jira] [Commented] (SOLR-18081) ShardRequestTracker should index by replica, not node

    [ https://issues.apache.org/jira/browse/SOLR-18081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055230#comment-18055230 ] 

ASF subversion and git services commented on SOLR-18081:
--------------------------------------------------------

Commit d766e9e723033d29e092242d5bba268e1590ea3a in solr's branch refs/heads/main from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=d766e9e7230 ]

SOLR-18081: ShardRequestTracker should use a unique key for requests (#4068)



> ShardRequestTracker should index by replica, not node
> -----------------------------------------------------
>
>                 Key: SOLR-18081
>                 URL: https://issues.apache.org/jira/browse/SOLR-18081
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Houston Putman
>            Assignee: Houston Putman
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Currently many of the Admin APIs will return a list of sub-request responses indexed by Node url. Since multiple sub-requests can be sent to a single node, such as if there are multiple replicas on that node, the response will not contain all sub-request responses.
> The solution is to index these responses by replica instead of by node.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org