Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates
 209.85.200.168 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=HXwjCZYi9yeZ/m2p/b7qDUCI6jhouW28ZA+5DCerWjk/Nmtw91bq8tNgisW2Yw3QXE
         s9Rpp5xX1UZtJrZUQAbMaY1rQeTxk7BFQ6ZSXAssyGTT18qGqS4TskmiCkvGTKqNzvo8
         YC6zFS6O7abkWQfZDyUGB1+X7W8p0N527NPlw=
Message-ID: <e282921e0809190626h3d101ffy96e13a75921ddb2a@mail.gmail.com>
Date: Fri, 19 Sep 2008 09:26:58 -0400
From: "Chris Anderson" <jchris@apache.org>
Sender: jchris@gmail.com
To: couchdb-user@incubator.apache.org
Subject: Re: replicating large db from version 0.8.1 to trunk (0.9.0a696354)
In-Reply-To: <928bdd8e0809170941s441338dp5ab3aed40306488@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <928bdd8e0809170941s441338dp5ab3aed40306488@mail.gmail.com>

Will,

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.

Chris

On Wed, Sep 17, 2008 at 12:41 PM, william kinney
<william.kinney@gmail.com> 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
http://jchris.mfdz.com