Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Doc - Update remark about per-database replication (#7891)

This commit is contained in:
Simran 2019-01-08 10:36:00 -08:00 committed by sleto-it
parent 28b84951cb
commit e7810e1956
2 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/Books/HTTP/Replications/README.md
View File

@ -16,8 +16,6 @@ The HTTP replication interface serves four main purposes:
- administer the replication applier (starting, stopping, configuring, querying state) on - administer the replication applier (starting, stopping, configuring, querying state) on
a slave a slave
Please note that all replication operations work on a per-database level. If an Please note that if a per-database setup is used (as opposed to server-level replication,
ArangoDB server contains more than one database, the replication system must be available since v3.3.0), then the replication system must be configured individually per
configured individually per database, and replicating the data of multiple database, and replicating the data of multiple databases will require multiple operations.
databases will require multiple operations.

8
Documentation/Books/Manual/Administration/MasterSlave/ReplicationApplier.md
View File

@ -7,7 +7,7 @@ Replication configuration
The replication is turned off by default. In order to create a master-slave setup, The replication is turned off by default. In order to create a master-slave setup,
the so-called _replication applier_ needs to be enabled on the _slave_ databases. the so-called _replication applier_ needs to be enabled on the _slave_ databases.
Replication is configured on a per-database level, or, starting from 3.3.0 at server level. Replication is configured on a per-database level or (starting from v3.3.0) at server level.
The _replication applier_ on the _slave_ can be used to perform a one-time synchronization The _replication applier_ on the _slave_ can be used to perform a one-time synchronization
with the _master_ (and then stop), or to perform an ongoing replication of changes. To with the _master_ (and then stop), or to perform an ongoing replication of changes. To
@ -20,7 +20,7 @@ _setupReplication_ Command
To copy the initial data from the _master_ to the _slave_ and start the To copy the initial data from the _master_ to the _slave_ and start the
continuous replication, there is an all-in-one command *setupReplication*. continuous replication, there is an all-in-one command *setupReplication*.
From _ArangoSH_: From _Arangosh_:
```js ```js
require("@arangodb/replication").setupReplication(configuration); require("@arangodb/replication").setupReplication(configuration);
@ -242,7 +242,7 @@ The initial synchronization for the current database is executed with the *sync*
require("@arangodb/replication").sync({ require("@arangodb/replication").sync({
endpoint: "tcp://master.domain.org:8529", endpoint: "tcp://master.domain.org:8529",
username: "root", username: "root",
password: "secret, password: "secret",
includeSystem: true includeSystem: true
}); });
``` ```
@ -259,7 +259,7 @@ The following command only synchronizes collection *foo* and *bar*:
require("@arangodb/replication").sync({ require("@arangodb/replication").sync({
endpoint: "tcp://master.domain.org:8529", endpoint: "tcp://master.domain.org:8529",
username: "root", username: "root",
password: "secret, password: "secret",
restrictType: "include", restrictType: "include",
restrictCollections: [ "foo", "bar" ] restrictCollections: [ "foo", "bar" ]
}); });