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 F1DDA98C5 for ; Tue, 5 Jun 2012 07:50:49 +0000 (UTC) Received: (qmail 46245 invoked by uid 500); 5 Jun 2012 07:50:48 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 46212 invoked by uid 500); 5 Jun 2012 07:50:48 -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 46187 invoked by uid 99); 5 Jun 2012 07:50:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 07:50:47 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dave@muse.net.nz designates 209.85.212.52 as permitted sender) Received: from [209.85.212.52] (HELO mail-vb0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 07:50:42 +0000 Received: by vbzb23 with SMTP id b23so3606181vbz.11 for ; Tue, 05 Jun 2012 00:50:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=muse.net.nz; s=google; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=Z0vgUfuucrWuQDTwvBrMUnMMYnSn/0SZ3qgyyOZQc08=; b=Qtx0+AEx6E8/UkN+KvZMVrzmLbD+Iu4NdGHT5fczKJzsfPmel58hAMVz535efPkWav xVg8JqaUqcTZou2DH638i0wwQFNP19Mr+4xR05Z0V3Ez8vUFhun6VQoLsShZaFi396fX q9g2Sa2ldshvqu/8OX1OSvOoUFqaSzF9sRnyw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding :x-gm-message-state; bh=Z0vgUfuucrWuQDTwvBrMUnMMYnSn/0SZ3qgyyOZQc08=; b=KTtjtlxD5U6MGLFXNkA9nRfRH0D1KHm+Vvwn3haYKObNtMDOlwjWjtqMxC5EfbTJxI ZwbLjZfi+iOP8mZEvxgEMq0rPBPcd4vWc/bcbX2GHcImc1XOnQkYxdynjo3vb2WoWTTk BSYd8zYG9mQbUFDMkbKey1P2RR8mC3a76KIzKXQ47Cb0as1al+wVe8aJj4TyJhyQkUax Hk2eWfOebb+Usk3uku2xADNDv9VpKTdsiMhPvGRpRDKyVHvCYCZpnWS8a4JyfB2qItT6 c8muMSTzK836rz7gtW4Ur+tKXAu5XgJOa8y6GZKQyqhMSfiGmnEQ8Olb9xOgThREfcne FBgg== MIME-Version: 1.0 Received: by 10.220.8.17 with SMTP id f17mr15152273vcf.11.1338882621467; Tue, 05 Jun 2012 00:50:21 -0700 (PDT) Received: by 10.52.33.172 with HTTP; Tue, 5 Jun 2012 00:50:21 -0700 (PDT) X-Originating-IP: [84.112.19.176] In-Reply-To: References: Date: Tue, 5 Jun 2012 09:50:21 +0200 Message-ID: Subject: Re: limit on number of docs updated via _bulk_docs? From: Dave Cottlehuber To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkhGueldHfWi8szI0IdKRqRPW3kd2aFMiVpvFqTtKfBPa8NXysspRknJlSI7FKehXhCUIQn X-Virus-Checked: Checked by ClamAV on apache.org On 5 June 2012 05:07, Tim Tisdall wrote: > Hopefully someone can give me an idea on this problem because I think > I've about exhausted ideas. > > I'm doing a series of document updates fairly rapidly. =A0I was doing > the updates via PUT and was having no problems except for the DB file > size growing way too fast. =A0I changed things to update the database in > batches using _bulk_docs. =A0Now I seem to have a problem with > connections timing out to couchdb after about 11000 doc updates. =A0I've > tried different size batches from 5 to 500 docs but each time the > program dies with a connection time out after about the same number of > doc updates. > > I thought it may be a problem with my code (it's in PHP, and that's > usually the problem ;) ), however I tried something that I think > negates that possibility. =A0I have the script running and stop it after > about 5000 updates, then manually restart the script again right away. > =A0The second time the script dies after about 6000 updates. =A0So, still > around 11000 updates over 2 different processes. > > Any thoughts, guesses, things to try, or things to test? > > -Tim I'd start off with putting the couch into [log] level =3D debug and see wha= t comes out. Feel free to put a section up on friendpaste.com or similar for commen= t. A+ Dave