8000 Remove things related to Mesos and DC/OS from 3.3 and 3.4 (#241) · arangodb/docs@80b9234 · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Dec 13, 2023. It is now read-only.

Commit 80b9234

Browse files
authored
Remove things related to Mesos and DC/OS from 3.3 and 3.4 (#241)
1 parent 689ec6a commit 80b9234

29 files changed

+17
-1017
lines changed

3.3/administration-replication-asynchronous-limitations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ removed in later versions of ArangoDB:
3232
* master servers do not know which slaves are or will be connected to them. All servers
3333
in a replication setup are currently only loosely coupled. There currently is no way
3434
for a client to query which servers are present in a replication.
35-
* when not using our mesos integration failover must be handled by clients or client APIs.
35+
* failover must be handled by clients or client APIs.
3636
* there currently is one replication applier per ArangoDB database. It is thus not
3737
possible to have a slave apply operations from multiple masters into the same target
3838
database.

3.3/cookbook/cloud-dcos-full-example.md

Lines changed: 0 additions & 189 deletions
This file was deleted.

3.3/cookbook/cloud-mesos-containers.md

Lines changed: 0 additions & 59 deletions
This file was deleted.

0 commit comments

Comments
 (0)
0