You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/03/09 01:25:38 UTC
[jira] [Commented] (KUDU-1913) Tablet server should handle failure
gracefully instead of crashing
[ https://issues.apache.org/jira/browse/KUDU-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902278#comment-15902278 ]
Todd Lipcon commented on KUDU-1913:
-----------------------------------
I think it's running out of threads on a tablet server. We have some plans to reduce the number of threads created - right now we create at least two per partition on a tablet server, so if you try to put many thousands of partitions on one server, you'll hit this. The known limitations document does recommend keeping to hundreds of tablets per server max in current versions.
> Tablet server should handle failure gracefully instead of crashing
> ------------------------------------------------------------------
>
> Key: KUDU-1913
> URL: https://issues.apache.org/jira/browse/KUDU-1913
> Project: Kudu
> Issue Type: Bug
> Reporter: Juan Yu
>
> When adding lots of range partitions, all tablet server crashed with the following error:
> F0308 14:51:04.109369 12952 raft_consensus.cc:1985] Check failed: _s.ok() Bad status: Runtime error: Could not create thread: Resource temporarily unavailable (error 11)
> Tablet server should handle error/failure more gracefully instead of crashing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)