couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-613) Compaction tasks crash
Date Tue, 05 Jan 2010 15:20:55 GMT

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

Robert Newson commented on COUCHDB-613:
---------------------------------------

Hi,

Sorry, I don't currently have any more information than this. I wanted to report it while
I still had what little information I had on screen. CouchDB is responsive after this event
without restarting it but since this happens in my automated overnight tests I can't say how
immediately it recovers.

All I know is that I was left with an incomplete .compact file for every single database (a
dozen or so) on each of the three servers I tested this on and no active tasks on any of them.
I figured that was pretty extraordinary. I agree that it's not likely that the client issuing
the _compact calls or the one calling _active_tasks is the cause of the crash.

Sorry I don't have more information at this time, I'll be on IRC after I conduct an interview
today and perhaps we can chat about this?

> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message