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 2016/05/17 04:54:13 UTC

[jira] [Resolved] (KUDU-1450) LogBlockManager start-up is slow due to MemTracker atomic contention

     [ https://issues.apache.org/jira/browse/KUDU-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon resolved KUDU-1450.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.0

Fixed in 2c0ac84e1de6c2df2768eb664cdb1f7f43e74119

> LogBlockManager start-up is slow due to MemTracker atomic contention
> --------------------------------------------------------------------
>
>                 Key: KUDU-1450
>                 URL: https://issues.apache.org/jira/browse/KUDU-1450
>             Project: Kudu
>          Issue Type: Bug
>          Components: fs, perf
>    Affects Versions: 0.8.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.9.0
>
>         Attachments: fg.svg
>
>
> I'm looking at startup time on a cluster with lots of data per node. On this cluster, the tablet server takes about 30 seconds to start the LogBlockManager, and appears CPU bound. I grabbed a profile and it seems like most of the CPU is spent in MemTracker::Release and Consume (see attached flame graph).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)