According the stats replicator had written all the docs it read. Did new changes happened in source db while replication was active? In the logs you could try to check which document was replicated the last, then read database changes until the same document and see which comes after. If problem is there, you'll have a chance to inspect it. Also, you try to start another replication since the update_seq of the last replicated document to see if anything will happens. -- ,,,^..^,,,
On Sun, Dec 28, 2014 at 9:53 PM, Cory Zue <[email protected]> wrote: > Hey, > > We're trying to replicate a legacy Couch 1.2.1 database onto a cloudant > database, but it keeps getting stuck. We are initiating the replication on > our server, and setting the target to our cloudant DB. However, it is not > checkpointing at all and appears to be getting stuck after about 1.6 > million documents. Here is the example status from our database: > > {"pid": "<0.5351.0>","checkpointed_source_seq": 2,"continuous": true,"doc_id > ": null,"doc_write_failures": 0,"docs_read": 1615106,"docs_written": 1615106 > ,"missing_revisions_found": 1615106,"progress": 0,"replication_id": " > 212f656bae3da2d25d6ca31d20d8537e+continuous","revisions_checked": 1615106," > source": "http://admin:*****@localhost:5984/dbname/ > <http://admin:*****@localhost:5984/commcarehq/>","source_seq": 10153797," > started_on": 1419615219,"target": " > http://user:*****@user.cloudant.com/dbname-backup/ > <http://commcarehq:*****@commcarehq.cloudant.com/commcarehq-india-backup/>", > "type": "replication","updated_on": 1419780400}, > > It has a been in this state for more than 24 hours, and starting a similar > job without continuous replication yielded the same results. > > Are there any known issues replicating from couch 1.2.1 to cloudant? Or is > there another way we could initiate the replication that is more likely to > succeed? Anything we should look for in log files? > > thanks, > Cory
