[
https://issues.apache.org/jira/browse/COUCHDB-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672727#action_12672727
]
Chris Anderson commented on COUCHDB-246:
----------------------------------------
Curently, sending log() responses occasionally is all it takes to prevent a
time out. I'm not suggesting that we don't need a special keep-alive
intermediate response, just that it should be fairly trivial to crib from what
the log case does, and, if you can't wait for the patch, you can use log() as a
stand in.
> 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.
