Hi Robert, Thanks for your help. That API was not familiar to me. However I realized my issue. It was due to a break in connectivity between the source and the target database servers (Target server was pulling). However this failure was silent. The replication (on fauxton) did not show any sort of failure. It said "Running" and "Continuonus" as if all was well, and the only indication of an issue was that the "Active Tasks" section didnt include the replication jobs as well. I have fixed the connectivity issue, and the jobs are running now. But I find this silent failure behaviour very wierd. Is it intended? Or a bug?
Thanks, Karthik T On Mon, 29 Oct 2018, 12:46 AM Robert Samuel Newson, <rnew...@apache.org> wrote: > Hi, > > We introduced a new replicator scheduler after 2.0 which I think moved > where replication status appears. > > http://docs.couchdb.org/en/stable/api/server/common.html#scheduler-jobs > http://docs.couchdb.org/en/stable/api/server/common.html#scheduler-docs > > So check /_scheduler/jobs and /_scheduler_docs next. > > B. > > > On 26 Oct 2018, at 15:37, Karthik T <sir.nigel.lor...@gmail.com> wrote: > > > > Hi All, > > > > I am attempting to upgrade our Production db from 1.6.1 to 2.1.1. I am > > attempting this by replicating from my old box running 1.6.1 to my newly > > rebuilt box running 2.1.1. It seemed to go ok so far. I was planning to > > switch my app over to the new box once the data was replicated, and the > > views were regenerated (I have a daemon triggering this on the main views > > on the new box) and the DB compacted. > > > > I say "seemed" because now it seems like replication(of all the things > :() > > has stopped. I can create the replications/replicator documents, it tells > > me the replication has been "Scheduled", and the replication jobs shows > the > > new job as "running". However the replication jobs that used to populate > > the "Active Tasks" view are now gone. And I can confirm that the > > replication isnt happening by manually comparing documents on the 2 > boxes. > > > > I wonder if in all my restarts getting the config changed, I broke > > something. Specifically is there a replicator daemon that I might have > > broken?? > > > > Karthik T > >
