You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Dinesh Kumar Naik (Jira)" <ji...@apache.org> on 2021/11/11 07:32:00 UTC
[jira] [Updated] (SOLR-14298) LBSolrClient.checkAZombieServer
should be less stupid
[ https://issues.apache.org/jira/browse/SOLR-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Kumar Naik updated SOLR-14298:
-------------------------------------
Attachment: image-2021-11-11-13-01-24-975.png
> 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-01-24-975.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.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org