[COUCHDB-782] Restarting replication

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.10
• Component/s: Replication
• Labels: replication

Environment

Ubuntu, 9.10

• Skill Level: Regular Contributors Level (Easy to Medium)
• Assignee: Unassigned
• Reporter: Till Klampaeckel
• Created: 02/Jun/10 16:02
• Updated: 02/Sep/18 06:28
• Resolved: 02/Sep/18 06:28

Description

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"}

' http://localhost:5984/_replicate

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":"http://user:[e-mail]:5984/foo", "target":"http://remote:5984/foo"}

' http://user:[e-mail]:5984/_replicate

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.

Issue Links

• blocks: COUCHDB-477 Add database uuid's