incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Vander Wilt (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (COUCHDB-1429) Server stops responding after heavy load against _list function
Date Mon, 05 Mar 2012 20:35:59 GMT
Server stops responding after heavy load against _list function
---------------------------------------------------------------

                 Key: COUCHDB-1429
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1429
             Project: CouchDB
          Issue Type: Bug
    Affects Versions: 1.1.1
         Environment: Ubuntu 11.10 on AWS EC2 t1.micro instance, ~512MB memory and no swap
            Reporter: Nathan Vander Wilt


Under heavy load, CouchDB crashes and stops responding to all incoming requests.

To reproduce this, basically:
1. build-couchdb (1.1.1) on an EC2 t1.micro running Ubuntu
2. Add the '42' file at the path Blitz.io is looking for (not sure the easiest way to do this
natively, I inserted a rule for it at the nginx level)
3. Run their default rush on a _list function (mine happened to do a fair amount of work,
doing a Markdown conversion and Mustache templating)
4. Around about the 40 concurrent user mark in my case, CouchDB dies a terrible horrible death
with a
bunch of zombie couchjs process.

In this log https://gist.github.com/a059c4db5bce19f1df7f (warning: large!) you'll see the
heavy requests being handled but suddenly crashing. The "restart" seen at the end was due
to manual intervention from the shell, CouchDB did not gracefully handle the issue.

I later tried turning on some swap space in case memory was an issue, but didn't seem to have
an appreciable effect.

May be related to the discussion here: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201203.mbox/%3cCAPinO9ek5xAjLLpYufwnRk3hxkn5e-5j59pR6ummdWpMthhuuA@mail.gmail.com%3e

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