cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11390) Too big MerkleTrees allocated during repair
Date Tue, 22 Mar 2016 10:46:25 GMT


Marcus Eriksson commented on CASSANDRA-11390:

This assumes all ranges contain equally many keys, so this could create too deep trees for
small ranges and then not deep enough for the big ranges. Maybe we should factor in how many
% of the keys are in a given range?

Say the current range is responsible for 10% of the total number of partitions, it should
then be allowed to allocate at most {{0.1 * 2^20}} merkle tree nodes?

> Too big MerkleTrees allocated during repair
> -------------------------------------------
>                 Key: CASSANDRA-11390
>                 URL:
>             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

View raw message