You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2016/03/21 15:46:25 UTC
[jira] [Updated] (CASSANDRA-11390) Too big MerkleTrees allocated
during repair
[ https://issues.apache.org/jira/browse/CASSANDRA-11390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-11390:
----------------------------------------
Reviewer: Marcus Olsson
Status: Patch Available (was: Open)
patch here: https://github.com/krummas/cassandra/commits/marcuse/merkletree
tests:
https://cassci.datastax.com/view/Dev/view/krummas/job/krummas-marcuse-merkletree-dtest/
https://cassci.datastax.com/view/Dev/view/krummas/job/krummas-marcuse-merkletree-testall/
Can you review [~molsson]?
> 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)