cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8639) Can OOM on CL replay with dense mutations
Date Tue, 24 Nov 2015 22:49:11 GMT


Ariel Weisberg commented on CASSANDRA-8639:

Proposed change. Adding a limit on the number of bytes was easy. Writing a unit test was not
so easy. I refactored CommitLogReplayer so you can spy on the mutations it initiates. Suggestions
for a better way to test this new behavior are welcome.

|[2.1 code|]|[utests|]|[dtests|]|
|[2.2 code|]|[utests|]|[dtests|]|
|[3.0 code|]|[utests|]|[dtests|]|

> Can OOM on CL replay with dense mutations
> -----------------------------------------
>                 Key: CASSANDRA-8639
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Assignee: Ariel Weisberg
>            Priority: Minor
>             Fix For: 2.1.x
> If you write dense mutations with many clustering keys, the replay of the CL can quickly
overwhelm a node on startup.  This looks to be caused by the fact we only ensure there are
1000 mutations in flight at a time. but those mutations could have thousands of cells in them.
> A better approach would be to limit the CL replay to the amount of memory in flight using

This message was sent by Atlassian JIRA

View raw message