From user-return-21973-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Tue Sep 4 12:26:35 2012 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 57370D965 for ; Tue, 4 Sep 2012 12:26:35 +0000 (UTC) Received: (qmail 56187 invoked by uid 500); 4 Sep 2012 12:26:33 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 55839 invoked by uid 500); 4 Sep 2012 12:26:31 -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 55795 invoked by uid 99); 4 Sep 2012 12:26:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2012 12:26:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of luke.driscoll@gmail.com designates 209.85.214.180 as permitted sender) Received: from [209.85.214.180] (HELO mail-ob0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2012 12:26:23 +0000 Received: by obceq6 with SMTP id eq6so10175816obc.11 for ; Tue, 04 Sep 2012 05:26:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=t/BhkB6Mf/rHJOj5iaibdBicDzoAnG628MepEIQNBzQ=; b=yyuGOKHw0KxxpwTb5fSYmh1xLRjltJV+9iElKedNOYomNAbOmxxhYLFdSypJsKy0Xg 7KLbiL9+7UOU34gxjXQs1uCg9/bVz5raiukL8ulmDOd+p5U6nCcCi6JH41Joz3P65nTA tEBrFzJdgqjqK6MA68JpzWySGI4wbhfj7hJzDYS795nx0Cfr9Eq4LiZxuICz88XDMaYI +7lBS/F+66FbUUHXKwyhuPbU39pcp0YH+atobL0bDNlhi6JpK9/v6Ez9D4hm54WTLu7q bXZGFrVZUjdDanUCMnuADBmAAH32QC3fHAdvfCQKZPAzhkuL/9dLhM2AyUHpHLSy6nR0 F1DA== Received: by 10.182.154.70 with SMTP id vm6mr16510907obb.50.1346761562109; Tue, 04 Sep 2012 05:26:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.39.104 with HTTP; Tue, 4 Sep 2012 05:25:41 -0700 (PDT) In-Reply-To: References: From: Luke Driscoll Date: Tue, 4 Sep 2012 08:25:41 -0400 Message-ID: Subject: Re: CouchDB and Elasticsearch on same machine To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=f46d04479f0b81b6f104c8df5c3e --f46d04479f0b81b6f104c8df5c3e Content-Type: text/plain; charset=ISO-8859-1 We run this set up in QA with no real trouble, although we don't have very high traffic on that box. I would suggest you give the box a couple of cnames, like test-couchdb and test-elasticsearch; then when you create the indices on test-elasticsearch you point them to test-couchdb; this should help separation in the future. Luke On 3 September 2012 21:39, Thomas Hommers wrote: > Hi, > > for a first small "testing" deployment of our application I would like to > run CouchDB and elasticsearch on the same machine to save some costs. After > demand grows i plan to separate them. > > Does anybody have experience with this, any specific issues to take care > of? > > I remember that several times i faced a problem with heavy CPU + memory > usage of couchdb. Is there any way to limit this, so it will nicely > co-exists with Elasticsearch? I read that elasticsearch makes trouble when > the system starts swaping ... > > Really appreciate any thoughts and comments. > > Thanks in advance! > Thomas --f46d04479f0b81b6f104c8df5c3e--