cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-7646) DROP may not clean commit log segments when auto snapshot is false
Date Thu, 11 Sep 2014 05:46:34 GMT

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

Benedict resolved CASSANDRA-7646.
---------------------------------
    Resolution: Not a Problem

I was mistaken when I thought this was also an issue: we don't special case drop at all, we
always flush on it. No calls to renewMemtable which is the danger zone.

> DROP may not clean commit log segments when auto snapshot is false
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-7646
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7646
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jeremiah Jordan
>            Assignee: Benedict
>             Fix For: 2.0.11
>
>
> Per discussion on CASSANDRA-7511 DROP may also be affected by the same issue.  If auto
snapshot is false, commit log segments may stay dirty because they are not flushed.



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

Mime
View raw message