From 3bb8367ff434c6a033e8a3dda771d619b57ed22c Mon Sep 17 00:00:00 2001 From: jsteemann Date: Thu, 8 Jun 2017 22:16:00 +0200 Subject: [PATCH] removed one known issue that was fixed in the meantime --- Documentation/Books/Manual/ReleaseNotes/KnownIssues32.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/Documentation/Books/Manual/ReleaseNotes/KnownIssues32.md b/Documentation/Books/Manual/ReleaseNotes/KnownIssues32.md index 40ccba1049..578f39277d 100644 --- a/Documentation/Books/Manual/ReleaseNotes/KnownIssues32.md +++ b/Documentation/Books/Manual/ReleaseNotes/KnownIssues32.md @@ -32,7 +32,7 @@ are present in the MMFiles engine: are split into multiple smaller RocksDB transactions that are committed individually. The entire user transaction will not necessarily have ACID properties in this case. - The thresholds values for transaction sizes can be configured globally using the + The threshold values for transaction sizes can be configured globally using the startup options * `--rocksdb.intermediate-commit-size`: if the size of all operations in a transaction @@ -55,10 +55,7 @@ The following known issues will be resolved in future releases: * the RocksDB engine is not yet performance-optimized and potentially not well configured -* the edge index in the RocksDB engine is not memory-optimized. It has a cache that will - currently use more memory than expected. This will be changed after 3.2.beta is released - -* collections for which a geo index is present will use a collection-level write locks +* collections for which a geo index is present will use collection-level write locks even with the RocksDB engine. Reads from these collections can still be done in parallel but no writes