cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8499) Ensure SSTableWriter cleans up properly after failure
Date Tue, 06 Jan 2015 15:46:34 GMT

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

Marcus Eriksson commented on CASSANDRA-8499:
--------------------------------------------

2.1 v2 seems to double-close the files, first when we switch the writer, then when we call
abort(), running SSTableRewriterTest.testNumberOfFiles_abort() outputs this: WARN  15:43:17
close(81) failed, errno (9).

> Ensure SSTableWriter cleans up properly after failure
> -----------------------------------------------------
>
>                 Key: CASSANDRA-8499
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8499
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>             Fix For: 2.0.12
>
>         Attachments: 8499-20.txt, 8499-20v2, 8499-21.txt, 8499-21v2
>
>
> 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
(v6.3.4#6332)

Mime
View raw message