[
https://issues.apache.org/jira/browse/SOLR-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251594#comment-14251594
]
Ramkumar Aiyengar commented on SOLR-6324:
-----------------------------------------
I did look at seeing what I can do about optimize, but couldn't come up with
any approach short of rearchitecting optimize to be async which I didn't have
time for. The other possibility here was that we apply a different timeout on a
per request basis (which btw is generally useful and something i wished for),
but that ran to a dead end as well -- I don't recall why now..
The stale check removal does force an idle timeout, but the connection timeouts
still need to be made finite?
> 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: [email protected]
For additional commands, e-mail: [email protected]
