[
https://issues.apache.org/jira/browse/COUCHDB-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis updated COUCHDB-782:
--------------------------------------
Skill Level: Regular Contributors Level (Easy to Medium)
> Restarting replication
> -----------------------
>
> Key: COUCHDB-782
> URL: https://issues.apache.org/jira/browse/COUCHDB-782
> 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"}' 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:[email protected]:5984/foo";,
> "target":"http://remote:5984/foo"}'
> http://user:[email protected]: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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
