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 sebastiancohnen@googlemail.com
 designates 209.85.161.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=WxTKSyzTq8BBtu9YG+/Xcyv38XLYmtRNieApLwjLs/XbOBKtL206OVaB6bPXOBGrua
         8tqu2u0D8xCExMPiOEh/xOYrkKsXxyGO92Joumt5fa2KaSGXztGJ0jOQzWTxoISEekwe
         mtDhQUDl56W3FwZ02oMO3eKRZ7zeNdDEvRSXA=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: How to monitor continuous replication status?
From: Sebastian Cohnen <sebastiancohnen@googlemail.com>
In-Reply-To: <AANLkTilvilRVEbh0MkQyU40AHZft9lAJTv9KKPp1V1_c@mail.gmail.com>
Date: Mon, 5 Jul 2010 15:58:06 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E714D46-936C-411A-87B6-FD55078416E4@googlemail.com>
References: <AANLkTilHTWdLm3w_sLHH-gY4DgdFYx9LNkIGlBK7sdu9@mail.gmail.com>
 <AANLkTilvilRVEbh0MkQyU40AHZft9lAJTv9KKPp1V1_c@mail.gmail.com>
To: user@couchdb.apache.org

a little bit OT maybe, but wouldn't it be nice if _active_task would be =
a feed like _changes? So everyone who is interested in monitoring could =
simply consume the feed rather than having to poll and check for =
changes?

On 05.07.2010, at 15:53, Robert Newson wrote:

> Continuous replication tasks remain in _active_tasks until they are
> cancelled or fail (for example, by the remote end crashing).
>=20
> You can grep the front of the "task" string to match it to the
> returned _local_id or infer it from from the rest of the string. E.g,
>=20
> curl -X PUT http://localhost:5984/_replicate -d
> '{"source":"db1","target":"db2","continuous":true}'
>=20
> gives;
>=20
> {"ok":true,"_local_id":"56a810250d6aed082fa4aae1dc58fb6c"}
>=20
> If you poll /_active_tasks, you can see it's still alive;
>=20
> curl http://localhost:5984/_active_tasks
> [{"type":"Replication","task":"56a810: db1 ->
> db2","status":"Starting","pid":"<0.370.0>"}]
>=20
> I don't think you can get the timestamp for when couchdb last started,
> but I think the per-db "instance_start_time" is probably fine, since I
> believe it's used in finding replication checkpoints;
>=20
> curl http://localhost:5984/db2
> {"db_name":"db2" .... ,"instance_start_time":"1278337744957334"....}
>=20
> I believe there's an effort to persistent continuous replication tasks
> so that they are restarted if they fail, so hopefully the answers to
> these questions have only short-term validity.
>=20
> B.
>=20
> On Mon, Jul 5, 2010 at 7:47 AM, Rachel Willmer <rwillmer@gmail.com> =
wrote:
>> Once you have started a continuous replication, is there a way to
>> monitor that it is still running?
>>=20
>> For example, will it always be visible in _active_tasks even if there
>> is no active replication occurring?
>>=20
>> Or is there a URL you can ping, passing on the _local_id which is
>> given when you start the continuous replication?
>>=20
>> Or failing that, is there a URL on the couchdb server which returns
>> when it was last restarted?
>>=20
>> Rachel
>>=20