[kudu] branch master updated: docs: remove log_force_fsync_all known issue

[ad...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

adar pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git


The following commit(s) were added to refs/heads/master by this push:
     new 164d8d2  docs: remove log_force_fsync_all known issue
164d8d2 is described below

commit 164d8d20935e4adfb1f99e17ca81b3178d695a2b
Author: Adar Dembo <ad...@cloudera.com>
AuthorDate: Wed Dec 4 21:14:56 2019 -0800

    docs: remove log_force_fsync_all known issue
    
    This was fixed in KUDU-1125 (1.6.0) and should have been removed back then.
    
    Change-Id: I9f9ddb9924cdf4f59efeba8fc1bfa1ab6e063df5
    Reviewed-on: http://gerrit.cloudera.org:8080/14845
    Reviewed-by: Andrew Wong <aw...@cloudera.com>
    Reviewed-by: Alexey Serbin <as...@cloudera.com>
    Tested-by: Kudu Jenkins
    Reviewed-by: Grant Henke <gr...@apache.org>
---
 docs/known_issues.adoc | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/docs/known_issues.adoc b/docs/known_issues.adoc
index 52fe9e4..c8e2e5d 100644
--- a/docs/known_issues.adoc
+++ b/docs/known_issues.adoc
@@ -189,9 +189,6 @@ The following are known bugs and issues with the current release of Kudu. They w
 be addressed in later releases. Note that this list is not exhaustive, and is meant
 to communicate only the most important known issues.
 
-* If the Kudu master is configured with the `-log_force_fsync_all` option, tablet servers
-  and clients will experience frequent timeouts, and the cluster may become unusable.
-
 * If a tablet server has a very large number of tablets, it may take several minutes
   to start up. It is recommended to limit the number of tablets per server to 1000
   or fewer. Consider this limitation when pre-splitting your tables. If you notice slow