couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-613) Compaction tasks crash
Date Thu, 20 Oct 2011 00:23:11 GMT

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

Randall Leeds commented on COUCHDB-613:
---------------------------------------

Is this fixed with 1.1.1?
                
> Compaction tasks crash
> ----------------------
>
>                 Key: COUCHDB-613
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-613
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.11
>         Environment: debian 5.0, amd64, couchdb from git.apache.org at dd15c8ed5bf5873aec08a99a0687849f1d29f4c3
>            Reporter: Robert Newson
>
> I'm running repeated tests where I create multiple databases on multiple machines and
then compact them all in parallel. 
> This almost always works but sometimes does not. Specifically, I have one machine where
each .compact file is about 50% complete (I know this because I see successfully compacted
versions of the same data on the other machines in my set) and this in the log;
> [Mon, 04 Jan 2010 19:50:23 GMT] [error] [<0.17793.28>] Uncaught error in HTTP request:
{exit,noproc}
> [Mon, 04 Jan 2010 19:50:26 GMT] [error] [<0.17801.28>] Uncaught error in HTTP request:
{exit,noproc}
> [Mon, 04 Jan 2010 19:50:26 GMT] [error] [<0.17753.28>] Uncaught error in HTTP request:
{exit,noproc}
> I'm not sure it's related to the compact process crash but my http client also received
an error while polling _active_tasks for compaction to complete;
> Waiting for compaction to complete.
> Exception in thread "main" org.apache.http.conn.HttpHostConnectException: Connection
to http://machine_name:5984 refused

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

        

Mime
View raw message