Repository: kudu
Updated Branches:
  refs/heads/master b8cf59a2f -> 8478f026e


[docs] Add docs for 'Could not create thread' error

Change-Id: I1e24dc98a0f51a0af2d4959043ae80d44ba1ba0a
Reviewed-on: http://gerrit.cloudera.org:8080/10078
Reviewed-by: Adar Dembo <a...@cloudera.com>
Tested-by: Will Berkeley <wdberke...@gmail.com>
Reviewed-by: Todd Lipcon <t...@apache.org>


Project: http://git-wip-us.apache.org/repos/asf/kudu/repo
Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/a9bc168f
Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/a9bc168f
Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/a9bc168f

Branch: refs/heads/master
Commit: a9bc168f81f7fbd628569e1d0b5e0124399882f7
Parents: b8cf59a
Author: Will Berkeley <wdberke...@apache.org>
Authored: Mon Apr 16 13:51:26 2018 -0400
Committer: Will Berkeley <wdberke...@gmail.com>
Committed: Mon Apr 16 23:12:25 2018 +0000

----------------------------------------------------------------------
 docs/troubleshooting.adoc | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kudu/blob/a9bc168f/docs/troubleshooting.adoc
----------------------------------------------------------------------
diff --git a/docs/troubleshooting.adoc b/docs/troubleshooting.adoc
index 71b3771..51d412c 100644
--- a/docs/troubleshooting.adoc
+++ b/docs/troubleshooting.adoc
@@ -575,3 +575,20 @@ Users will encounter this exception when trying to use a 
Kudu table via Hive. Th
 is not a case of a missing jar, but simply that Impala stores Kudu metadata in
 Hive in a format that's unreadable to other tools, including Hive itself and 
Spark.
 There is no workaround for Hive users. Spark users need to create temporary 
tables.
+
+[[too_many_threads]]
+=== Runtime error: Could not create thread: Resource temporarily unavailable 
(error 11)
+
+Users will encounter this error when Kudu is unable to create more threads,
+usually on versions of Kudu older than 1.7. It happens on tablet servers, and
+is a sign that the tablet server hosts too many tablet replicas. To fix the
+issue, users can raise the `nproc` ulimit as detailed in the documentation for
+their operating system or distribution. However, the better solution is to
+reduce the number of replicas on the tablet server. This may involve rethinking
+the table's partitioning schema. For the recommended limits on number of
+replicas per tablet server, see the known issues and scaling limitations
+documentation for the appropriate Kudu release. The
+link:http://kudu.apache.org/releases/[releases page] has links to documentation
+for previous versions of Kudu; for the latest release, see the
+link:known_issues.html[known issues page].
+

Reply via email to