Remove documentation except DocuBlocks, covered by PR in docs repo

arangodb · KVS85 · Jul 22, 2019 · Jul 19, 2019 · Jul 19, 2019 · Jul 19, 2019
commit 0144f4ec1e0f877c0a80321be74127123b366c6a
diff --git a/Documentation/Books/Manual/Architecture/Replication/README.md b/Documentation/Books/Manual/Architecture/Replication/README.md
@@ -38,10 +38,6 @@ factor. The number of _followers_ can be controlled using the
 `replicationFactor` parameter is the total number of copies being
 kept, that is, it is one plus the number of _followers_. 
 
-In addition to the `replicationFactor` we have a `minReplicationFactor`
-that locks down a collection for writing as soon as we have lost too many followers.
-
-
 Asynchronous replication
 ------------------------
 

diff --git a/Documentation/Books/Manual/DataModeling/Collections/DatabaseMethods.md b/Documentation/Books/Manual/DataModeling/Collections/DatabaseMethods.md
@@ -164,15 +164,6 @@ to the [naming conventions](../NamingConventions/README.md).
   dramatically when using joins in AQL at the costs of reduced write
   performance on these collections.
 
-- *minReplicationFactor* (optional, default is 1):  in a cluster, this
-  attribute determines how many copies of each shard are required
-  to be in sync on the different DBServers. If we have less then these
-  many copies in the cluster a shard will refuse to write. The
-  minReplicationFactor can not be larger than replicationFactor.
-  Please note: during server failures this might lead to writes
-  not being possible until the failover is sorted out and might cause
-  write slow downs in trade of data durability.
-
 - *distributeShardsLike*: distribute the shards of this collection
   cloning the shard distribution of another. If this value is set,
   it will copy the attributes *replicationFactor*, *numberOfShards* and 

diff --git a/Documentation/Books/Manual/ReleaseNotes/NewFeatures35.md b/Documentation/Books/Manual/ReleaseNotes/NewFeatures35.md
@@ -217,18 +217,6 @@ operations in user-land AQL queries.
 Also see the [TTL Indexes](../Indexing/Ttl.md) page.
 
 
-Collections
------------
-
-All collections now support a minimum replication factor (minReplicationFactor) property.
-This is default set to `1`, which is identical to previous behavior.
-If in a failover scenario a shard of a collection has less than minReplicationFactor many insync followers it will go into "read-only" mode and will reject writes until enough followers are insync again.
-In more detail:
-Having `minReplicationFactor == 1` means as soon as a "master-copy" is available of the data
-writes are allowed.
-Having `minReplicationFactor > 1` requires additional insync copies on follower servers to allow writes.
-The feature is used to reduce the diverging of data in case of server failures and to help new followers to catch up.
-
 HTTP API extensions
 -------------------
 
@@ -277,12 +265,6 @@ Note that this requires client applications to abort transactions which are no
 longer necessary. Otherwise resources and locks acquired by the transactions
 will hang around until the server decides to garbage-collect them.
 
-### Minimal replication Factor
-
-Within the properties of a collection we can now define a minReplicationFactor.
-This affects all routes that can create or modify the properties of a collection, including
-the graph API `_api/gharial`. All places where a replicationFactor can be modified, can now
-modify the minReplicationFactor as well.
 
 Web interface
 -------------