cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-459) Commitlog segments don't get deleted
Date Mon, 28 Sep 2009 20:23:16 GMT

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

Jonathan Ellis commented on CASSANDRA-459:
------------------------------------------

New patches attached.

What was happening is that when a ColumnFamily got marked dirty in the commitlog, all subsequent
commitlog segments would also have that CF marked dirty, even after it was flushed.  When
flush happened it could clear out old segments, but if the CF never had any more updates (like
the LocationInfo CF in the system keyspace) then log segments would pile up.

This makes log segments only treat a CF as dirty if it actually has data written to it for
that CF.

> Commitlog segments don't get deleted
> ------------------------------------
>
>                 Key: CASSANDRA-459
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-459
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.4, 0.5
>
>         Attachments: 0001-logging.txt, 0002-CASSANDRA-459-flush-locationinfo-every-minute-and-hint.txt,
0003-cleanup-don-t-preserve-dirty-bits-from-older-replay-s.txt
>
>
> System table is not created with a periodic flush, so any update there (such as storing
token info) can prevent commitlog segments from being deleted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message