natas_hw
/
cassandra
mirror of https://github.com/apache/cassandra
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Elaborate on why we need to recycle CL segments when dropping tables 

patch by Aleksandr Sorokoumov; reviewed by Caleb Rackliffe and Benjamin Lerer for CASSANDRA-16986
This commit is contained in:
Aleksandr Sorokoumov 2021-09-27 15:33:32 +02:00 committed by Caleb Rackliffe
parent 13632e9a99
commit 35446dca27
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/java/org/apache/cassandra/db/commitlog/CommitLogSegmentManager.java
View File

@ -291,7 +291,8 @@ public class CommitLogSegmentManager
* Switch to a new segment, regardless of how much is left in the current one. * Switch to a new segment, regardless of how much is left in the current one.
* *
* Flushes any dirty CFs for this segment and any older segments, and then recycles * Flushes any dirty CFs for this segment and any older segments, and then recycles
* the segments * the segments. This is necessary to avoid resurrecting data during replay if a user
* creates a new table with the same name and ID. See CASSANDRA-16986 for more details.
*/ */
void forceRecycleAll(Iterable<UUID> droppedCfs) void forceRecycleAll(Iterable<UUID> droppedCfs)
{ {