Currently HttpShardHandlerFactory and DUH2 set socket and connection
timeouts to unlimited by default. Should there be some finite default
instead? With the current defaults, a machine crash for example will lead
to requests in progress hang and occupy threads till the process is shut
down, which doesn't seem desirable. These are all configurable, we could
set some default (60s for conn, 600s for socket?), let people know and have
them up the limits if they really need it..

Thoughts?

Reply via email to