[
https://issues.apache.org/jira/browse/SOLR-13458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126148#comment-17126148
]
Alexander Zhideev commented on SOLR-13458:
------------------------------------------
Thanks for your response. Similar is happening here - collections grow by many
millions per day and total volume is over 3 Billion docs. So far no luck on
fixing the timeouts that come and go. One approach which seems to sort of work
is by using commitWithinMs along with also allowing some time for cool down
between queries by not sending requests to Solr and then retrying on Timeout
exception. It literally throws 1 timeout after 2 mins then after a few minutes
of cool down period same query runs for 4-5 mins and returns just fine with no
issue
> Make Jetty timeouts configurable system wide
> --------------------------------------------
>
> Key: SOLR-13458
> URL: https://issues.apache.org/jira/browse/SOLR-13458
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Affects Versions: master (9.0)
> Reporter: Gus Heck
> Priority: Major
>
> Our jetty container has several timeouts associated with it, and at least one
> of these is regularly getting in my way (the idle timeout after 120 sec). I
> tried setting a system property, with no effect and I've tried altering a
> jetty.xml found at solr-install/solr/server/etc/jetty.xml on all (50)
> machines and rebooting all servers only to have an exception with the old 120
> sec timeout still show up. This ticket proposes that these values are by
> nature "Global System Timeouts" and should be made configurable in solr.xml
> (which may be difficult because they will be needed early in the boot
> sequence).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
