couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Klampaeckel (JIRA)" <>
Subject [jira] Commented: (COUCHDB-782) Restarting replication
Date Thu, 03 Jun 2010 15:45:08 GMT


Till Klampaeckel commented on COUCHDB-782:

Until I find time for the wiki:

The mechanism does not just depend on the host per se, all the following URIs are different
to CouchDB even though they point to the same system:


While you're at it doing UUIDs for databases, do you think it would be possible to do a UUID
for a server as well? It could be exposed with the version. It would be very useful in large
scale setups for monitoring etc.. E.g. to easily tell shards apart, etc.. Vs. building external
"logic" that revolves around hostnames, port numbers or different something.

> Restarting replication 
> -----------------------
>                 Key: COUCHDB-782
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 0.10
>         Environment: Ubuntu, 9.10
>            Reporter: Till Klampaeckel
> So we had to restart replication on a server and here's something I noticed.
> At first I restarted the replication via the following command from localhost:
> curl -X POST -d '{"source":"http://localhost:5984/foo", "target":"http://remote:5984/foo"}'
> In response, futon stats:
> W Processed source update #176841152
> That part is great.
> Last night I did not have immediate access to the shell so I restarted replication from
remote (through curl on my mobile):
> curl -X POST -d '{"source":"", "target":"http://remote:5984/foo"}'
> The response in futon this morning:
> W Processed source update #1066
> ... and it kept sitting there like it was stalled and only continued in smaller increments.
> I restarted CouchDB and restarted from localhost - instant jump to 176 million.
> I'm just wondering what might be different accept for that one is against the public
interface, vs. localhost. I'd assume that replication behaves the same regardless.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message