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 1B18AF5B1 for ; Wed, 1 May 2013 09:53:47 +0000 (UTC) Received: (qmail 76143 invoked by uid 500); 1 May 2013 09:53:45 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 75842 invoked by uid 500); 1 May 2013 09:53:45 -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 75815 invoked by uid 99); 1 May 2013 09:53:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 May 2013 09:53:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.214.172] (HELO mail-ob0-f172.google.com) (209.85.214.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 May 2013 09:53:38 +0000 Received: by mail-ob0-f172.google.com with SMTP id v19so1173775obq.31 for ; Wed, 01 May 2013 02:52:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=rp8uHQvbmRS5txk/T8jMpkMi7uMZ+fCbtJxMoP/J1OI=; b=LsjwW7CH6XKMLZENdoAAG0SluNv30gntJ3SWQT48Z9AjFaV79j8wX4KpM4azYI9kAS i03PWR3gPSAabILwHYm+BZAPYcjWaEHqJULRWzU5McemthyAvUQhETMLRfayhmbhpKqW QwI04884R97PD3paQKBXu2veLf1YJQBg8h1XIXybUk2LKXtA0Q4PleCncC/boQYg72P1 24oBwhYHCVGgsfd5s53euSj9ycDbRFF9KQgrFP5q964cigGTfwa4ot5ymf3p6mUq5cTG hrroKMdxqNZnrMm1LiNCcyULqYTZujehgMtncViORYwZKjSDyW9zS8RHc1W8dxqte1jz 7RLA== MIME-Version: 1.0 X-Received: by 10.60.29.161 with SMTP id l1mr472995oeh.111.1367401977752; Wed, 01 May 2013 02:52:57 -0700 (PDT) Received: by 10.182.64.78 with HTTP; Wed, 1 May 2013 02:52:57 -0700 (PDT) In-Reply-To: References: <3E6A7478-96CC-49CD-88B6-BF67FAFDE406@gmail.com> Date: Wed, 1 May 2013 11:52:57 +0200 Message-ID: Subject: Re: CouchDB 1.2.0 Keeps Crashing. From: Pieter van der Eems To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnPDlPH/mNl1YHBNrVmwbpdJAdWAQ+uyRrwQAENd0Yga4KefFsJypENn7Ov+StZzOOeaEks X-Virus-Checked: Checked by ClamAV on apache.org 2013/5/1 Robert Newson : > I'd set it to 10000 and then forget it about it. That sounds a bit high. > File descriptors are pretty cheap these days. That's what I thought about inodes as well but we've already hit that wall (tip: use xfs when using a lot of small files). Pieter. > > On 1 May 2013 10:29, Pieter van der Eems > wrote: >> 2013/5/1 Benoit Chesneau : >>> On Wed, May 1, 2013 at 11:00 AM, Pieter van der Eems >>> wrote: >>>> 2013/5/1 Benoit Chesneau : >>>>> On Wed, May 1, 2013 at 10:44 AM, Benoit Chesneau wrote: >>>>>> On Wed, May 1, 2013 at 10:38 AM, Pieter van der Eems >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> Is the file descriptor a couchdb limit that I can change (where?) or a >>>>>>> filesystem limit (ext4, we've already hit ext4 limit before but the >>>>>>> errors were different). >>>>>>> >>>>>>> >>>>>> >>>>>> man ulimit(3) >>>>>> >>>>>> - benoit >>>>> >>>>> >>>>> in clear, either use the ulimit command to increase the limits at >>>>> runtime or increase them either in security.conf or limits.conf >>>>> depending on your system. >>>> Ubuntu 11.10 (it needs updating, just haven't had the time yet). >>>> >>>>> >>>>> Probably /etc/security/limits.conf in your case. >>>> That looks like the one. >>>> >>>> >>>>> I'm actually >>>>> interrested by the limit you already have, can you paste the result of >>>>> ` ulimit -n` ? >>>> >>>> It's 1024 >>>> That seems to be the default. >>>> My own desktop (Ubuntu 12.04) has the same. >>>> >>>> We have more than that number of databases (1134 as of now). >>>> >>> >>> Thanks, you should try to slowly iincrease the limits of the user >>> launching couchdb to test which one is good for you, it all depends on >>> the number of max dbs opened, number of requests and view calculated >>> at the same time >> Hmm. I really should find the time to install a test server for this >> and create a simulation. Currently the only way to "test" this is on a >> live environment that serves live customers. >> >> For now I've set it to 2048. >> >> Regards, >> Pieter.