lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-6324) Set finite default timeouts for select and update
Date Thu, 27 Nov 2014 03:40:12 GMT


Mark Miller commented on SOLR-6324:

Agreed - we need timeouts of some fine length.

We may want to be even more conservative on the read timeout though - I'm on the fence. Really,
we have to consider what we want for something like an optimize request that takes 3 hours
to return. Do we care that the call will timeout? Probably something like that should be kicked
off and the status pulled, but we should still think about any standard long calls.

> Set finite default timeouts for select and update
> -------------------------------------------------
>                 Key: SOLR-6324
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message