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/22 15:52:41 UTC

[jira] [Commented] (KUDU-680) block cache limit seems to not be fully respected

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

Todd Lipcon commented on KUDU-680:
----------------------------------

I'm now able to reproduce this by starting a Kudu server and then inserting 7-8B rows into it via Impala. Interestingly, starting a server with the same settings and inserting twice as many rows using tpch_real_world doesn't seem to have the same magnitude effect.

> block cache limit seems to not be fully respected
> -------------------------------------------------
>
>                 Key: KUDU-680
>                 URL: https://issues.apache.org/jira/browse/KUDU-680
>             Project: Kudu
>          Issue Type: Bug
>          Components: tablet
>    Affects Versions: Private Beta
>            Reporter: Todd Lipcon
>         Attachments: screenshot-1.png, screenshot-2.png
>
>
> The ITBLL cluster configures block cache capacity to 512MB, but the memtracker is reporting 685MB of usage. It's clearly not un-bounded, because this server has been up for days doing lots of work, but we're either not properly counting the memory, or not properly respecting the configured limit. Maybe we're only counting the values and not the keys, or something of that nature.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)