cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh McKenzie (Jira)" <>
Subject [jira] [Commented] (CASSANDRA-14349) Untracked CDC segment files are not deleted after replay
Date Tue, 27 Jul 2021 19:04:00 GMT


Josh McKenzie commented on CASSANDRA-14349:

ack [~blerer]. This was merged in as commit

6edfe7fb50b2d0562282b12b07aba67e95a76940 back in 2018; failed to follow up here.


I'll close this out.

> Untracked CDC segment files are not deleted after replay
> --------------------------------------------------------
>                 Key: CASSANDRA-14349
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Local Write-Read Paths
>            Reporter: Shichao An
>            Assignee: Shichao An
>            Priority: Low
> When CDC is enabled, a hard link to each commit log file will be created in cdc_raw
directory. Those commit logs with CDC mutations will also have cdc index files created along
with the hard links; these are intended for the consumer to handle and clean them up.
> However, if we don't produce any CDC traffic, those hard links in cdc_raw will be never
cleaned up (because hard links will still be created, without the index files), whereas the
real original commit logs are correctly deleted after replay during process startup. This
will results in many untracked hard links in cdc_raw if we restart the cassandra process many
times. I am able to use CCM to reproduce it in trunk version which has the CASSANDRA-12148
> This seems a bug in handleReplayedSegment of the commit log segment manager which neglects
to take care of CDC commit logs. I will attach a patch here.

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message