[
https://issues.apache.org/jira/browse/SOLR-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228013#comment-14228013
]
Mark Miller commented on SOLR-6324:
-----------------------------------
Im still not happy about breaking optimize - it's a terrible user experience.
We need to change it to just kick off and not wait or something more sensible
than just breaking its current behavior for many, many cases by default.
> Set finite default timeouts for select and update
> -------------------------------------------------
>
> Key: SOLR-6324
> URL: https://issues.apache.org/jira/browse/SOLR-6324
> Project: Solr
> Issue Type: Improvement
> Components: search, update
> Reporter: Ramkumar Aiyengar
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 5.0, Trunk
>
>
> Currently {{HttpShardHandlerFactory}} and {{UpdateShardHandler}} default to
> infinite timeouts for socket connection and read. This can lead to
> undesirable behaviour, for example, if a machine crashes, then searches in
> progress will wait forever for a result to come back and end up using threads
> which will only get terminated at shutdown.
> We should have some finite default, however conservative it might be. These
> parameters are already configurable, so for expert uses, they can be
> increased if necessary anyway.
> Will attach a patch to set connection timeout to 60s and read timeout to
> 600s, but I am not too concerned about the actual value as long as there is
> one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
