Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of rwillmer@gmail.com designates
 72.14.220.157 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=BXOjfOx9hFgipfdW//KSV6/NIXX6VKUR2BjECKN86FZxf5xK8kpb/D3dJtIw/p+0zh
         3yT/tt7OMVt+y8jS8GkvOzoWczS6oC15X/CLXH9y58vyJ0dHHxCtLCbFnD17bhQcST2B
         TF+xAxWqIplxK/Wk2Czx7NNVcze/eUoxdmYXY=
MIME-Version: 1.0
Date: Wed, 21 Apr 2010 10:11:19 +0100
Message-ID: <r2r5cd112871004210211g274769e1l6752af7e61d8182f@mail.gmail.com>
Subject: can you detect consistency?
From: Rachel Willmer <rwillmer@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Say I have 2 couchdb nodes which replicate bi-directionally.

Is there a way of detecting that they have reached consistency?
(assuming that changes have stopped being made and that the
replication has done its thing)

By trial and error, I can see that in a scenario where I have two
nodes which do in fact have the same data (which I've verified by
scripting a doc-by-doc check that their revs are the same, and their
contents are the same); in that scenario, the update_seq is different
on the two nodes.

So I have 2 questions:

a) is that expected or a bug? (my guess is that it's expected)

b) is there any other way of detecting consistency quickly?

Rachel