cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11390) Too big MerkleTrees allocated during repair
Date Wed, 23 Mar 2016 07:47:25 GMT

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

Marcus Eriksson commented on CASSANDRA-11390:
---------------------------------------------

agreed, lets create a new ticket where we evaluate if we want to include the compaction gain
factor when estimating the trees (and maybe increase the maxDepth)

pushed a commit with log fixes (moved the logging to debug) and triggered new builds

> Too big MerkleTrees allocated during repair
> -------------------------------------------
>
>                 Key: CASSANDRA-11390
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11390
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 3.0.x, 3.x
>
>
> Since CASSANDRA-5220 we create one merkle tree per range, but each of those trees is
allocated to hold all the keys on the node, taking up too much memory



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

Mime
View raw message