couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antony Blakey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-246) allow customization of external process timeout
Date Wed, 11 Feb 2009 08:54:59 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672558#action_12672558
] 

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

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

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

> allow customization of external process timeout
> -----------------------------------------------
>
>                 Key: COUCHDB-246
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-246
>             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.


Mime
View raw message