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

Joshua Bronson commented on COUCHDB-275:
----------------------------------------

updated to r749851 as jan___ in #couchdb told me about a file descriptor leak 
prior to r748299, and retried compaction. this time compaction appears to have 
successfully completed, at least the following was output to couch.log:

[Wed, 04 Mar 2009 23:19:23 GMT] [debug] [<0.8952.0>] CouchDB swapping files 
/var/lib/couchdb/melkjug.couch and /var/lib/couchdb/melkjug.couch.compact.

however, 11 seconds later (adjusting for my local time of GMT-5) the erlang vm 
appears to have crashed again: the following was output to stderr:

heart: Wed Mar  4 18:19:34 2009: heart-beat time-out.
heart: Wed Mar  4 18:19:39 2009: Unable to kill old process, kill failed (tried 
multiple times).
heart: Wed Mar  4 18:19:40 2009: Executed "/usr/bin/couchdb -k". Terminating.

> couch crashes erlang vm under heavy load
> ----------------------------------------
>
>                 Key: COUCHDB-275
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-275
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.9
>         Environment: Linux melkjug.com 2.6.23-gentoo-r8 #1 SMP Wed Feb 13 
> 14:28:49 EST 2008 x86_64 QEMU Virtual CPU version 0.9.1 GenuineIntel GNU/Linux
>            Reporter: Joshua Bronson
>
> I clicked "Compact" in futon for my 11G database at 9:04 AM EST:
> [Mon, 02 Mar 2009 14:04:32 GMT] [info] [<0.59.0>] Starting compaction for db 
> "melkjug"
> An hour and a half later it was 85% finished and then the following was 
> output to stderr:
> heart: Mon Mar  2 10:33:20 2009: heart-beat time-out.
> /usr/bin/couchdb: line 255: echo: write error: Broken pipe
> heart: Mon Mar  2 10:33:22 2009: Executed "/usr/bin/couchdb -k". Terminating.
> I am retaining my 4.3G melkjug.couch.compact file in case it's useful in 
> debugging this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to