This is an automated email from the ASF dual-hosted git repository.
adar pushed a commit to branch branch-1.9.x
in repository https://gitbox.apache.org/repos/asf/kudu.git
The following commit(s) were added to refs/heads/branch-1.9.x by this push:
new 7ec64d9 known_issues: document fault tolerant scan memory issue
7ec64d9 is described below
commit 7ec64d99b2b5742d49ed662f279521a8b6ae9693
Author: Adar Dembo <[email protected]>
AuthorDate: Mon Apr 22 21:28:23 2019 -0700
known_issues: document fault tolerant scan memory issue
Change-Id: Ic0f1396da853e8e2863c6ba5dc0d32dba79b8e5f
Reviewed-on: http://gerrit.cloudera.org:8080/13081
Tested-by: Adar Dembo <[email protected]>
Reviewed-by: Grant Henke <[email protected]>
---
docs/known_issues.adoc | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/docs/known_issues.adoc b/docs/known_issues.adoc
index 2370bed..88e6ba5 100644
--- a/docs/known_issues.adoc
+++ b/docs/known_issues.adoc
@@ -201,3 +201,10 @@ to communicate only the most important known issues.
or fewer. The maximum allowed number of tablets per server is 2000.
Consider this limitation when pre-splitting your tables. If you notice slow
start-up times,
you can monitor the number of tablets per server in the web UI.
+
+* Unlike regular scans, fault tolerant scans will allocate all required memory
+ when the scan begins rather than as it progresses. This can be significant
for
+ tablets of non-trivial size. Moreover, this memory usage isn't counted
towards
+ the tablet server's overall memory limit, raising the likelihood of the
tablet
+ server being out-of-memory killed by the kernel. See
+ link:https://issues.apache.org/jira/browse/KUDU-2466[KUDU-2466] for details.
