You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Eli Stevens (JIRA)" <ji...@apache.org> on 2014/04/02 02:40:16 UTC
[jira] [Commented] (COUCHDB-2218) gen_server timeout has unhelpful
error message
[ https://issues.apache.org/jira/browse/COUCHDB-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957192#comment-13957192 ]
Eli Stevens commented on COUCHDB-2218:
--------------------------------------
This commit was added to address the underlying issue:
https://github.com/apache/couchdb/commit/d81619033206f09a774072dc2f84f7f275b12496
Can progress be made when this occurs? IOW, is it possible for retrying to eventually work through task and allow the HTTP API call to succeed?
> gen_server timeout has unhelpful error message
> ----------------------------------------------
>
> Key: COUCHDB-2218
> URL: https://issues.apache.org/jira/browse/COUCHDB-2218
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JavaScript View Server
> Reporter: Eli Stevens
>
> It's not clear if this error is something that's actionable by the user or not:
> https://gist.github.com/wickedgrey/d2c87e6ee1e7c695abae
> It sounds like there's a bug ("sloppy") here, but I'm not certain.
> From IRC discussion:
> 4:40 PM rnewson: oh that's annoying
> 4:40 PM Wohali: gen_server timeout
> 4:40 PM rnewson: yeah, do we do a default timeout there for a view build? that's sloppy
> 4:40 PM Wohali: i bet, as it's not an os_process timeout
> 4:41 PM Wohali: which is what i would have expected to see
> 4:42 PM rnewson:
> run(Pid, IdxState) ->
> gen_server:call(Pid, {update, IdxState}).
> 4:42 PM wickedgrey: the machine was in the middle of a test run at the time, which processes a lot of data under somewhat high load (roughly O(num_cores)), but we do this regularly and don't usually see this
> 4:42 PM rnewson:
> couch_index_updater
> ah, this one;
> update(Mod, State) ->
> update(nil, Mod, State).
--
This message was sent by Atlassian JIRA
(v6.2#6252)