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] [Assigned] (CASSANDRA-8124) Stopping a node during compaction can make already written files stay around
Date Fri, 17 Oct 2014 14:02:33 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcus Eriksson reassigned CASSANDRA-8124:
------------------------------------------

    Assignee: Marcus Eriksson

> Stopping a node during compaction can make already written files stay around
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8124
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8124
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>              Labels: triaged
>             Fix For: 2.1.2
>
>
> In leveled compaction we generally create many files during compaction, in 2.0 we left
the ones we had written as -tmp- files, in 2.1 we close and open the readers, removing the
-tmp- markers.
> This means that any ongoing compactions will leave the resulting files around if we restart.
Note that stop:ing the compaction will cause an exception and that makes us call abort() on
the SSTableRewriter which removes the files.
> Guess a fix could be to keep the -tmp- marker and make -tmplink- files until we are actually
done with the compaction.



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

Mime
View raw message