Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: BigCouch merge - conflict management
From: Adam Kocoloski <kocolosk@apache.org>
In-Reply-To: <2945B9EFA9ECEF45930797FB76EE7A403501AC@SYD1214>
Date: Wed, 30 Apr 2014 07:29:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7A2BC2D-599D-47BF-9B85-49E74F3A3150@apache.org>
References: <2945B9EFA9ECEF45930797FB76EE7A403501AC@SYD1214>
To: user@couchdb.apache.org

Hi Klaus, N is the number of replicas of each document, not the number =
of nodes in the cluster.  You could have a 30 node cluster with N=3D1 =
and spread a database across all those nodes (Q >=3D 30). With N=3D1 =
you'll still have the consistency properties that you desire. Regards,

Adam

On Apr 30, 2014, at 3:46 AM, Schroiff, Klaus =
<KlausS@fast.au.fujitsu.com> wrote:

> Hi Joan,
>=20
> My thoughts circled more around N=3Dx (-say- 5) ,W=3D1,R=3D1.
> Or to phrase it differently - we'd like to use horizontal scaling =
whereas HA is not achieve in the same cluster but via (external) =
replication.
>=20
> So in this case the behaviour is still the same as with N=3DW=3DR=3D1 =
?
>=20
> Thanks
>=20
> Klaus