Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of Will.Perry@microsoft.com
 designates 207.46.163.152 as permitted sender)
Received-SPF: softfail (mail134-ch1: transitioning domain of microsoft.com
 does not designate 157.56.240.21 as permitted sender)
 client-ip=157.56.240.21; envelope-from=Will.Perry@microsoft.com;
 helo=BL2PRD0310HT003.namprd03.prod.outlook.com ;.outlook.com ;
From: Will Perry <Will.Perry@microsoft.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Subject: RE: Understanding 'Source database out of sync' error
Thread-Topic: Understanding 'Source database out of sync' error
Thread-Index: Ac6BfX4/OGnS8WZPRHyF/9KURiAzSgAAi+4AAAA4xGA=
Date: Mon, 15 Jul 2013 17:29:47 +0000
Message-ID: 
 <44836ba5384b4951b1058c7e1134befb@BLUPR03MB150.namprd03.prod.outlook.com>
References: 
 <931d322264da4d14ab604a10ad2a4ac2@BLUPR03MB150.namprd03.prod.outlook.com>
 <CABvT1DHL2H-oZrZF-6PM5dhjp+xbyuKcr9TS8UVvA_U9XSpy-A@mail.gmail.com>
In-Reply-To: 
 <CABvT1DHL2H-oZrZF-6PM5dhjp+xbyuKcr9TS8UVvA_U9XSpy-A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thanks for the speedy reply.

When running the scenario, each node only has one user db (plus, of course =
_replicator and _users) - there's a repl. Relationship setup for the existi=
ng db, but I can't see how I'd get anywhere near 100 open dbs with this set=
up.

Might it help to 'warm up' these new dbs by running a few queries against t=
hem before trying to replicate?

Cheers,

Will

-----Original Message-----
From: Robert Newson [mailto:rnewson@apache.org]=20
Sent: Monday, July 15, 2013 10:21 AM
To: user@couchdb.apache.org
Subject: Re: Understanding 'Source database out of sync' error

The replicator checks the instance_start_time of both servers and restarts =
the replication if they change. This is essential to ensure we replicate ev=
erything. The reason it recommends increasing max_dbs_open is that instance=
_start_time only changes if the database has previously closed, and this is=
 commonly because the LRU has done so.

Does it sound plausible that you have more actively replicating databases a=
t either end than your current max_dbs_open value? I believe the default va=
lue is 100.

B.


On 15 July 2013 18:09, Will Perry <Will.Perry@microsoft.com> wrote:
> Hi Folks,
>
> I'm seeing the following error pop up when attempting to write a new docu=
ment into the _replicator database referencing a newly created database:
>
> checkpoint_commit_failure,<<"Source database out of sync. Try to=20
> increase max_dbs_open at the source's server.">>
>
> The scenario I'm running is:
>
> 1.       On 2 couch nodes A and B
>
> 2.       Create a new database named 'Foo' on A, then on B
>
> 3.       Create a replication relationship on A to pull changes from B
>
> 4.       Create a replication relationship on B to pull changes from A
>
> This is failing at step 3 with a 400 (bad request) and Couch's logs are s=
howing me the error above. Incidentally, the same code used to work (on 1.2=
) - is there a known issue or workaround?
>
> Cheers,
>
> Will