8000 Update remark about per-database replication by Simran-B · Pull Request #7891 · arangodb/arangodb · GitHub
[go: up one dir, main page]
Skip to content

Update remark about per-database replication #7891

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 8, 2019
Merged

Update remark about per-database replication #7891

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a9fe840
Update remark about per-database replication
Simran-B Jan 6, 2019
641951f
Minor fixes to ReplicationApplier.md
Simran-B Jan 6, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions Documentation/Books/HTTP/Replications/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,6 @@ The HTTP replication interface serves four main purposes:
- administer the replication applier (starting, stopping, configuring, querying state) on
a slave

Please note that all replication operations work on a per-database level. If an
ArangoDB server contains more than one database, the replication system must be
configured individually per database, and replicating the data of multiple
databases will require multiple operations.

Please note that if a per-database setup is used (as opposed to server-level replication,
available since v3.3.0), then the replication system must be configured individually per
database, and replicating the data of multiple databases will require multiple operations.
8 changes: 4 additions & 4 deletions Documentation/Books/Manual/Administration/MasterSlave/ReplicationApplier.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Replication configuration
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.

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
with the _master_ (and then stop), or to perform an ongoing replication of changes. To
Expand All @@ -20,7 +20,7 @@ _setupReplication_ Command
To copy the initial data from the _master_ to the _slave_ and start the
continuous replication, there is an all-in-one command *setupReplication*.

From _ArangoSH_:
From _Arangosh_:

```js
require("@arangodb/replication").setupReplication(configuration);
Expand Down Expand Up @@ -242,7 +242,7 @@ The initial synchronization for the current database is executed with the *sync*
require("@arangodb/replication").sync({
endpoint: "tcp://master.domain.org:8529",
username: "root",
password: "secret,
password: "secret",
includeSystem: true
});
```
Expand All @@ -259,7 +259,7 @@ The following command only synchronizes collection *foo* and *bar*:
require("@arangodb/replication").sync({
endpoint: "tcp://master.domain.org:8529",
username: "root",
password: "secret,
password: "secret",
restrictType: "include",
restrictCollections: [ "foo", "bar" ]
});
Expand Down
0