couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <>
Subject [jira] Commented: (COUCHDB-246) allow customization of external process timeout
Date Wed, 11 Feb 2009 07:12:59 GMT


Paul Joseph Davis commented on COUCHDB-246:

Adding a configurable timeout would be simple. I should've added this during the original
writing of this code. I'm assuming though that when I wrote the original I thought, "Not important
until someone complains."

Either way, the time has come.

Adding a configurable timeout is trivial. I'll add an initial patch tomorrow most likely that
would grant some *.ini control for this.

In regards to Antony's comments I definitely agree, having a more dynamic timeout mechanism
would be best, but would require me more than the expected 10 or so lines of code.

Antony, also, when you say Keep-Alive, do you mean a heart beat to CouchDB or all the way
through to the HTTP client? I'd assume just to CouchDB in terms of a "Back off mofo, I'm still
working!" sort of way which we don't have yet.

In another slightly unlreated context, I contemplated the other day passing a UUID with all
 requests to os_process's. This would allow an asynchronous communication protocol for all
things dealing with non-erlang code. In terms of view servers, we could possibly push some
effort into the different view servers. I think it could also simplify internal code quite
a bit. The only thing that makes me push less hard is the fact that everything is happening
over stdio. I know that its optimized through the kernel and I don't have benchmarks to show
that it's a bottleneck, but its like a large pink flamingo standing there staring at me.

> allow customization of external process timeout
> -----------------------------------------------
>                 Key: COUCHDB-246
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.9
>            Reporter: Robert Newson
>            Priority: Blocker
>             Fix For: 0.9
> If an external process takes too long to respond, it is killed. The timeout is quite
short (a few seconds) and is not configurable from .ini files today.
> couchdb-lucene could use this ability as the first attempt to sort on a field in a large
index is slow while it builds a cache. With the timeout, it's killed and the partial work
is lost.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message