couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Davis <>
Subject Re: [jira] Commented: (COUCHDB-246) allow customization of external process timeout
Date Wed, 11 Feb 2009 18:54:05 GMT
On Wed, Feb 11, 2009 at 3:54 AM, Antony Blakey (JIRA) <> wrote:
>    [
> Antony Blakey commented on COUCHDB-246:
> ---------------------------------------
> I mean a keep-alive back to couch, not to the HTTP server, although the ability to propagate
the keep-alive as an HTTP continue might be interesting, though I'm not sure of the HTTP continue
> The keep-alive was trivial - 2/3 lines to handle the message, because IIRC the timeout
is in the receive loop of the external driver. I think its not more work than the configurable

That's a good point, unless there are objections, I'll throw this in as well.

> As far as UUIDs are concerned, do you mean session multiplexing over the _external channel?

That's exactly what I was thinking.

>> 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