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 6719AD29E for ; Sun, 7 Oct 2012 09:05:07 +0000 (UTC) Received: (qmail 7773 invoked by uid 500); 7 Oct 2012 09:05:05 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 7627 invoked by uid 500); 7 Oct 2012 09:05:05 -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 7601 invoked by uid 99); 7 Oct 2012 09:05:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Oct 2012 09:05:04 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of north.n@gmail.com designates 209.85.223.180 as permitted sender) Received: from [209.85.223.180] (HELO mail-ie0-f180.google.com) (209.85.223.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Oct 2012 09:04:59 +0000 Received: by mail-ie0-f180.google.com with SMTP id e10so6927292iej.11 for ; Sun, 07 Oct 2012 02:04:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jkXHZ1c9yymK4G0wEc1+2m+P+U/0P4Lq+MPSzrmDuUE=; b=I2z6ubtxbPEq1Xx7l7QjGkRMukG4L4qCwAfGLTSJHjGB/hHuGfNqqayy8tlz1v4dEL OBls/tcq0lk7QCRrx5XT3UdknsMpJ9YmlEXEuGJ5GbeA/XU3XRCZbQHwUCJ3zFu1w3ZE aCAezKh0gpQQJIzHENkMjMu0vcTUCI4o1CrVQyyKwYnXiIMfQDDJzH+o8RnJs8sNF5O5 6MXgkKHfMDvf38KVj1sn9QY56U0m+2da5P9Du/b9QZCVdnmRheSS88murpGVdthJUne5 QuYCtEFq4XguXCES8k2zbjS9v1Kh5wWRLMLQbIudc4qx2ChNBQxs9qLlDqRGjuGEJvEr a83w== MIME-Version: 1.0 Received: by 10.50.183.135 with SMTP id em7mr3130669igc.31.1349600678965; Sun, 07 Oct 2012 02:04:38 -0700 (PDT) Received: by 10.64.87.162 with HTTP; Sun, 7 Oct 2012 02:04:38 -0700 (PDT) In-Reply-To: References: Date: Sun, 7 Oct 2012 10:04:38 +0100 Message-ID: Subject: Re: Simple load-balancing replication best practices From: Nick North To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=14dae93407490eefc604cb7465c9 X-Virus-Checked: Checked by ClamAV on apache.org --14dae93407490eefc604cb7465c9 Content-Type: text/plain; charset=ISO-8859-1 I'm also interested in whether there is a preference for push or pull with CouchDb 1.2. I have a full-mesh replication setup using pull replication, but have no idea whether push might be better in some way. Is there a replication guru out there who could enlighten us? Nick On 4 October 2012 17:48, Dave Cottlehuber wrote: > On 4 October 2012 17:04, Steve Koppelman > wrote: > > Assuming a hubless (i.e. not master-slave) set of 4 couchdb 1.2.0 > > servers behind a load balancer, is there a recommended best-practice > > for setting up the replication relationships? I'm most interested in: > > > > * Assuming the _replicator document is on one of the two nodes in a > > relationship, is there a preference for push vs. pull replication > > relationships? I seem to recall pull as being regarded as more > > reliable than push through 1.1.1. > > Hope somebody else comments on this, I'm interested to know if this > still makes a difference. > > > --14dae93407490eefc604cb7465c9--