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

Yuki Morishita commented on CASSANDRA-10680:
--------------------------------------------

Patch is ready for review.

| 2.1 | 2.2 | 3.0.x (3.1) |
| [branch|https://github.com/yukim/cassandra/tree/10680] | 
[branch|https://github.com/yukim/cassandra/tree/10680-2.2] | 
[branch|https://github.com/yukim/cassandra/tree/10680-3.0] |
| 
[testall|http://cassci.datastax.com/view/Dev/view/yukim/job/yukim-10680-testall/lastCompletedBuild/testReport/]
 | 
[testall|http://cassci.datastax.com/view/Dev/view/yukim/job/yukim-10680-2.2-testall/lastCompletedBuild/testReport/]
 | 
[testall|http://cassci.datastax.com/view/Dev/view/yukim/job/yukim-10680-3.0-testall/lastCompletedBuild/testReport/]
 |
| 
[dtest|http://cassci.datastax.com/view/Dev/view/yukim/job/yukim-10680-dtest/lastCompletedBuild/testReport/]
 | 
[dtest|http://cassci.datastax.com/view/Dev/view/yukim/job/yukim-10680-2.2-dtest/lastCompletedBuild/testReport/]
 | 
[dtest|http://cassci.datastax.com/view/Dev/view/yukim/job/yukim-10680-2.2-dtest/lastCompletedBuild/testReport/]
 |

> Deal with small compression chunk size better during streaming plan setup
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10680
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10680
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jeff Jirsa
>            Assignee: Yuki Morishita
>             Fix For: 2.1.x
>
>
> For clusters using small compression chunk size and terabytes of data, the 
> streaming plan calculations will instantiate hundreds of millions of 
> compressionmetadata$chunk objects, which will create unreasonable amounts of 
> heap pressure. Rather than instantiating all of those at once, streaming 
> should instantiate only as many as needed for a single file per table at a 
> time.



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

Reply via email to