From user-return-17769-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Thu Sep 1 13:36:26 2011 Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 897788561 for ; Thu, 1 Sep 2011 13:36:26 +0000 (UTC) Received: (qmail 45873 invoked by uid 500); 1 Sep 2011 13:36:25 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 45816 invoked by uid 500); 1 Sep 2011 13:36:24 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 45808 invoked by uid 99); 1 Sep 2011 13:36:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 13:36:24 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_FROM,HTML_FONT_FACE_BAD,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of feinberg.scott@gmail.com designates 209.85.212.52 as permitted sender) Received: from [209.85.212.52] (HELO mail-vw0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 13:36:17 +0000 Received: by vws16 with SMTP id 16so2057747vws.11 for ; Thu, 01 Sep 2011 06:35:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=MSJkCUANzMQJdu1M5quhd0e3JTTLbMROUjJvQXeRbEw=; b=ThNw3FNzrvwwAqX1OMHcPoKIsGcvq8KrD0v/nPlQq78BT2Drl2mhldzSz0v6Hj2kqf mROEIc8KLJHDucSV5VrjurQrEb7AsKgTftIcOrR3/0pSQA8X3EPW50fkMSWB4TEUQNkQ D9KIFNWa9J+5eFhycVuXLs5vAs9MxhRr4cczI= Received: by 10.52.113.67 with SMTP id iw3mr241260vdb.290.1314884157101; Thu, 01 Sep 2011 06:35:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.182.202 with HTTP; Thu, 1 Sep 2011 06:35:37 -0700 (PDT) In-Reply-To: References: From: Scott Feinberg Date: Thu, 1 Sep 2011 09:35:37 -0400 Message-ID: Subject: Re: CouchDB 1.1 issue To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=bcaec547ca011ad74604abe15399 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec547ca011ad74604abe15399 Content-Type: text/plain; charset=ISO-8859-1 I haven't had that issue-though I'm not using using 1.1 in a production environment, just using it to replicate like crazy (millions of docs in each of my 20+ databases). I was running a server with 1 GB of memory and didn't have an issue, it handled it fine. However... from http://docs.couchbase.org/couchdb-release-1.1/index.html When you PUT/POST a document to the _replicator database, CouchDB will attempt to start the replication up to 10 times (configurable under [replicator], parameter max_replication_retry_count). Not sure if that helps. --Scott On Thu, Sep 1, 2011 at 9:28 AM, kowsik wrote: > Ran into this twice so far in production CouchDB in the last two days. > We are running CouchDB 1.1 on an EC2 AMI with multi-master replication > across two regions. I notice that every now and then CouchDB will > simply suck up 100% CPU 50% of the total memory and not respond at > all. So far the logs only show sporadic replication errors. One of the > stack traces (failed to replicate after 10 times) is about 500,000 > lines long. We are using the _replicator database. > > Anyone else running into this? Since 1.1 doesn't have the > try-until-infinity-and-beyond mode, we have a worker task that watches > the _replication_state and kicks the replicator as soon as it errors > out. Are there any settings in terms replicator memory usage, etc that > could help us? > > Thanks! > > K. > --- > http://blog.mudynamics.com > http://blitz.io > @pcapr > --bcaec547ca011ad74604abe15399--