couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "Replication" by FilipeManana
Date Wed, 22 Jun 2011 12:45:20 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "Replication" page has been changed by FilipeManana:
http://wiki.apache.org/couchdb/Replication?action=diff&rev1=31&rev2=32

Comment:
Removed wrong information and information that applies only to the new replicator (not yet
in any official release)

  
  == Replication at startup ==
  
- Since CouchDB 1.1.0, a system database `_replicator` is used to manage replications that
must be initialized at startup.
+ Since CouchDB 1.1.0, a system database named `_replicator` can be used to manage replications.
Replications triggered by POSTing to /_replicate/ (the old API) are not managed by this system
database.
+ The currently most reliable documentation about it can be found at:
  
- The _replicator database can be modified by CouchDB admins or by users which have the `_replicator`
role.
+ https://gist.github.com/832610  (from the author)
  
- The following fields are available:
+ http://docs.couchbase.org/couchdb-release-1.1/index.html#couchb-release-1.1-replicatordb
 (verifed by the author) 
  
- {{{
- {
-   _id: ...
- 
-   /* These are the same as the regular replication parameters */
-   source: "source-uri"
-   target: "target-uri"
-   filter: "document-name/filter-name"
-   query_params: {"name":"value",..}
-   continuous: true|false
-   doc_ids: ["id","id",...]
- 
-   /* These are handled by the replicator process to perform additional tasks. */
-   cancel: true|false
-   create_target: true|false
- 
-   /* Used to authenticate who can modify the record. */
-   user_ctx: {
-     "name":"user's name",
-     "roles":[...]
-   }
- 
-   /* These parameters control the behavior of the replicator process.
-      They may also be set in the configuration file under the `replicator` section. */
-   worker_processes: integer
-   worker_batch_size: integer
-   http_connections: integer
-   http_pipeline_size: integer
-   connection_timeout: integer
-   socket_options: [{keepalive, true}, {nodelay, false}]
- }
- }}}
- 
- Additionally the replicator uses configuration parameters:
- {{{
- [replicator]
- ssl_certificate_max_depth = 3
- verify_ssl_certificates = true|false
- ssl_trusted_certificates_file = ...
- 
- # Default values for the field of the same name in a _replicator document.
- worker_processes: integer
- worker_batch_size: integer
- http_connections: integer
- http_pipeline_size: integer
- connection_timeout: integer
- socket_options: [{keepalive, true}, {nodelay, false}]
- }}}
- 
- Also, as of CouchDB 1.1.0, the replicator process will only connect to a _replicator database
located on a non-SSL (plain http) CouchDB server. In other words if you plan to use the _replicator
database it must be hosted on a server that offers at least a non-SSL interface; the replicator
process however knows how to replicate databases which use SSL.
- 

Mime
View raw message