couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson" <>
Subject Re: replicating large db from version 0.8.1 to trunk (0.9.0a696354)
Date Fri, 19 Sep 2008 13:26:58 GMT

You can monitor the size of the .couch files that should be in the
database_dir as specified in the default.ini or local.ini files. (on
the version couch.ini on the old version)

The ini files should be at /usr/local/etc/couchdb/...

The file size won't be a perfect indication of how long the
replication has left, but it's better than nothing.


On Wed, Sep 17, 2008 at 12:41 PM, william kinney
<> wrote:
> Hi,
> I believe I heard at jchris's presentation at arc90 that the replicator can
> continue from a previously failed replication (continuing where it left
> off). Does anyone know if it is possible to monitor a replication process
> somehow, perhaps by log file or physical file size growth? I have a large db
> I'm trying to migrate from an old release to a new one, and it seems that
> (outside a small tool to loop and do the migration myself), the replicator
> is my only option since the db files (and views) use a deprecated storage
> design. My db is ~ 330000 docs (1.9GB).
> Or does anyone has a better idea for migrating a large, older version
> database?
> Thanks,
> Will

Chris Anderson

View raw message