forked from apache/cassandra
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Limit the number of L0 sstables by waiting for compaction.
Summary: With large key space (billions number of keys), cassandra repair creates over 4000 L0 sstables and cause regression in read performance. See https://issues.apache.org/jira/browse/CASSANDRA-11432 for detailed sympton. As we discuss with the community in https://issues.apache.org/jira/browse/CASSANDRA-10862, one way they suggest is we doing the compaction before make repaired table available for read. However, with my investigation, there are several issues/problem with this approach: - The compaction code is strongly coupled with compactionmanager, which has limit apis to schedule compactions as we wanted, and also it's not guaranteed to be executed. - Also there is no easy way to manage sstables without make them available to read. So, instead, we here introduced a different approach: Don't add the sstables for reading before the number of L0 sstables smaller than a configerable threshold. Since the compaction is always running, this is guaranteeded that after some time, the number of sstables in L0 will be reduced after compaction.
- Loading branch information
Showing
4 changed files
with
84 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters