-
Notifications
You must be signed in to change notification settings - Fork 225
_replicate vs _replication API endpoints #346
Comments
FYI
|
Creating Replications There are two ways to create replications:
Each are slightly different. For the transient ones there is no document backing the replication job. If the server crashes the job will just disappear. When jobs finish there is no way to query their state. This method of replicating was implemented initially.
The reason there are two is because Monitoring Replications
http://docs.couchdb.org/en/latest/api/server/common.html#scheduler-jobs
http://docs.couchdb.org/en/latest/api/server/common.html#get--_scheduler-docs-replicator_db Replication States Replication documents become replication jobs and then replication jobs do all the replication work. There are a number of states a replication goes through so this chart might be helpful: http://docs.couchdb.org/en/latest/replication/replicator.html#replication-states |
what about |
|
@ufobat do you have everything you need to write a PR? |
@wohali I think I do, thank you :-) |
I am not sure if and where i should mention the |
I am currently writing a little script that helps me to setup a replication between two couchdbs. Therefore I want to read the current replication jobs, check if my desired job is already there. If not, I would setup a replication. If there are jobs that are no longer required (doesnt match my criteria) I wanted to remove the those.
While doing so I was falling in some traps:
In the Replication Section of the documentation there are
_replication
and_replicate
. It took me a while to realize that those two are actually not the same names.First I send my "replication requests" into
_replicate
instead of_replication
. It took several minutes before something showed up in_schedule/jobs
. I was confused that there was no way to show my configuration immediatly. What is the expected behaviour when you configure a replication to_replicate
and what is the expected behaviour when you write it to_replication
?I would like to have some information in the documentation
that there are actually those two, and explain what is used for which usecase. (I dont know it, could you give me to write a PR, please)
that explains the expected behaviour in way like: When you do X you can see Y after Z happend.
(Like When you write to
_replicate
it takes at least x seconds x secons and then you can find the results in_schedule/jobs
- not sure if that is correct)If you could provide me some information I will gladly write a PR. :-)
The text was updated successfully, but these errors were encountered: