You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Filipe Manana (Commented) (JIRA)" <ji...@apache.org> on 2011/11/04 14:21:00 UTC

[jira] [Commented] (COUCHDB-1333) views hangs, time-out occurs, error probably related to COUCHDB-1246

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

Filipe Manana commented on COUCHDB-1333:
----------------------------------------

This is likely because your server is busy and the internal Erlang processes are using Erlang's gen_server default call timeout of 5 seconds which isn't enough for such cases (Erlang is soft real time).
I've hit this a few times as well, so updating those timeouts to 'infinity' should do it (for me it did at least).
                
> views hangs, time-out occurs,  error probably related to COUCHDB-1246
> ---------------------------------------------------------------------
>
>                 Key: COUCHDB-1333
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1333
>             Project: CouchDB
>          Issue Type: Bug
>          Components: JavaScript View Server
>    Affects Versions: 1.1.1
>         Environment: centos 5.5
>            Reporter: Armen Arsakian
>              Labels: javascript
>
> My permanent views are stalled, get responses never arrive from couchdb utill a time-out error occurs.
> Once I managed to get the following error:
> timeout {gen_server,call,[couch_query_servers,{get_proc,<<"javascript">>}]} 
> I found the following similar issue
> https://issues.apache.org/jira/browse/COUCHDB-1246
>  but this was closed at 18/8/2011.
> I guess this is not fixed yet, I  installed couchDB from source which I downloaded today, version: 1.1.1
> Is this issue still open.
> In my opensuse I have not any problem with views. version 1.1.0
> but in production machine a centos 5.5 i get the above error. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira