[
https://issues.apache.org/jira/browse/SOLR-17792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004787#comment-18004787
]
ASF subversion and git services commented on SOLR-17792:
--------------------------------------------------------
Commit 2a5cc9d97b059d8264b8a80d386ca205e4c1e8a9 in solr's branch
refs/heads/main from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=2a5cc9d97b0 ]
SOLR-17792: Fix deadlocks in ParallelHttpShardHandler (#3398)
Re-do the way that HttpShardHandler does synchronization
> ParallelHttpShardHandler has massive performance issues.
> --------------------------------------------------------
>
> Key: SOLR-17792
> URL: https://issues.apache.org/jira/browse/SOLR-17792
> Project: Solr
> Issue Type: Bug
> Affects Versions: 9.8
> Reporter: Houston Putman
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 9.9
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> SOLR-17158 changed the way that the HttpShardHandler (And
> ParallelHttpShardHandler) did locking and concurrency. However, after
> upgrading, and running distributed queries (at a relatively slow rate), I
> noticed that there were 3 types of responses:
> * QTimes between 3-6ms
> * QTimes between 53-56 ms
> * And requests that timed out
> Looking at the logic in HttpShardHandler, there is a poll(50ms) call that is
> very suspicious, and likely the reason for the jump between 3-6 ms and 53-56
> ms. I would also assume that this change in concurrency logic is the reason
> that many requests started timing out. Changing to the
> HttpShardHandlerFactory from the ParallellHttpShardHandlerFactory fixed these
> issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
