You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2017/07/20 00:22:00 UTC

[jira] [Commented] (KUDU-1913) Tablet server runs out of threads when creating lots of tablets

    [ https://issues.apache.org/jira/browse/KUDU-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093998#comment-16093998 ] 

Adar Dembo commented on KUDU-1913:
----------------------------------

Quick update: more progress has been made via commits 3fb84a7f9d235b3fa44393a0f197411922538e8c (consensus: consolidate Raft thread pools), 74d67fd2b7c8ad9c315f0b9894a49616e00e235d (server: consolidate tablet prepare pools), and 1070e764d97ce496325a277b9093f0ab3b9ee167 (consensus_peers: schedule raft heartbeats through messenger). These should be part of 1.5.

I'm currently working on (what I believe is) the last piece: consolidation of threads used in Raft failure detectors.


> Tablet server runs out of threads when creating lots of tablets
> ---------------------------------------------------------------
>
>                 Key: KUDU-1913
>                 URL: https://issues.apache.org/jira/browse/KUDU-1913
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: consensus, log
>            Reporter: Juan Yu
>            Assignee: Adar Dembo
>              Labels: data-scalability
>
> 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.4.14#64029)