On Sep 20, 2009, at 1:39 PM, Benoit Chesneau wrote:
On suggestion of jan I repost it here.
---------- Forwarded message ----------
From: Benoit Chesneau <[email protected]>
Date: Sun, Sep 20, 2009 at 7:06 PM
Subject: continuous replication questions
To: [email protected]
Hi,
I've done today some tests with replications (currently 1000 continous
replications open). From a remote node to another. So I have 1000 http
connections opened from one node to another. Seem to work well.
But I wonder what happened if one replication link hangs. Is there a
way to know a database isn't anymore replicated except by parsing
status ? Could we retrieve the lists of running replications maybe not
by HTTP but with Erlang ? Would be useful since such thing could
happened on so many open connections.
In Erlang you can do
supervisor:which_children(couch_rep_sup)
to get the full list of replications initiated on that node since the
last VM restart. Any replication with an undefined process id is no
longer running. It's of limited utility, though, because the IDs are
opaque and there's no easy way to figure out which IDs map to which
replication configurations. _active_tasks remains your best bet for
now.
Regards, Adam
