You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by "raj.yadav" <ra...@cse.ism.ac.in> on 2020/12/06 19:54:16 UTC
Re: Timeout occured while waiting response from server
Hey Karl,
Can you elaborate more about your system? How many shards does your
collection have, what is replica type? Are you using an external zookeeper?
Its looks like (from logs) that you are running solr on SolrCloud mode?
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Timeout occured while waiting response from server
Posted by "raj.yadav" <ra...@cse.ism.ac.in>.
elivis wrote
> See:
> https://lucene.472066.n3.nabble.com/SolrServerException-Timeout-occured-while-waiting-response-from-server-tc4464632.html
>
> Maybe this will help somebody. I was dealing with exact same problem. We
> are
> running on VMs, and all of our timeout problems went away after we
> switched
> from a 5yo VmWare version to the latest Hyper-V VMs. We also made sure
> that
> all VMs have a dedicated spindle. It appears the underlying physical disk
> drive (which all VMs use) was getting overloaded with reads/writes.
Hey Elivis,
Thanks for the quick response.
We are not getting `IOException` neither there is any iowait during commit.
We use curl command to issue commit and its not starting commit command on
all the shards at the same time.
You can find details about it here:
https://lucene.472066.n3.nabble.com/SOLR-8-5-2-Commit-through-curl-command-is-causing-delay-in-issuing-commit-tp4466276.html
Do let me know, in case you have any suggestions about this.
Regards,
Raj
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Timeout occured while waiting response from server
Posted by elivis <el...@basistech.com>.
See:
https://lucene.472066.n3.nabble.com/SolrServerException-Timeout-occured-while-waiting-response-from-server-tc4464632.html
Maybe this will help somebody. I was dealing with exact same problem. We are
running on VMs, and all of our timeout problems went away after we switched
from a 5yo VmWare version to the latest Hyper-V VMs. We also made sure that
all VMs have a dedicated spindle. It appears the underlying physical disk
drive (which all VMs use) was getting overloaded with reads/writes.
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html