[
https://issues.apache.org/jira/browse/SOLR-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762710#comment-17762710
]
Dinesh Kumar Naik commented on SOLR-14298:
------------------------------------------
[~noble.paul] thats also an option , but if there is possibility to make it
configurable at server side then it would be even better.
> LBSolrClient.checkAZombieServer should be less stupid
> -----------------------------------------------------
>
> Key: SOLR-14298
> URL: https://issues.apache.org/jira/browse/SOLR-14298
> Project: Solr
> Issue Type: Bug
> Reporter: Chris M. Hostetter
> Priority: Major
> Attachments: image-2021-11-11-13-11-30-930.png,
> image-2021-11-11-13-13-20-791.png
>
>
> LBSolrClient.checkAZombieServer() currently does /select query for {{\*:\*}}
> with distrib=false, rows=0, sort=\_docid\_ ... but this can still chew up a
> lot of time if the shard is big, and it's not self evident wtf is going on in
> the server logs.
> At a minimum, these requests should include some sort of tracing param to
> identify the point of he query (ie: {{_zombieservercheck=true}}) and should
> probably be changed to hit something like the /ping handler, or the node
> status handler, or if it's important to folks that it do a "search" that
> actaully uses the index searcher, then it should use options like
> timeAllowed / segmentTerminateEarly, and/or {{q=-\*:\*}} instead .. or maybe
> a cusorMark ... something to make it not have the overhead of counting all
> the hits.
--
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
