mirror of https://github.com/apache/cassandra
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:
parent
13632e9a99
commit
35446dca27
|
|
@ -291,7 +291,8 @@ public class CommitLogSegmentManager
|
|||
* 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
|
||||
* 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)
|
||||
{
|
||||
|
|
|
|||
Loading…
Reference in New Issue