cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8499) Ensure SSTableWriter cleans up properly after failure
Date Fri, 19 Dec 2014 17:31:14 GMT


Benedict commented on CASSANDRA-8499:

Everytime we fail to complete a flush or compaction we will leak the bloom filter data, so
it is probably not _that_ uncommon. It's also a pretty small fix. But pretty agnostic about
it, really, since clusters seem to have been surviving with it for years.

> Ensure SSTableWriter cleans up properly after failure
> -----------------------------------------------------
>                 Key: CASSANDRA-8499
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>             Fix For: 2.0.12
>         Attachments: 8499-20.txt, 8499-21.txt
> In 2.0 we do not free a bloom filter, in 2.1 we do not free a small piece of offheap
memory for writing compression metadata. In both we attempt to flush the BF despite having
encountered an exception, making the exception slow to propagate.

This message was sent by Atlassian JIRA

View raw message