Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-10862

LCS repair: compact tables before making available in L0

    XMLWordPrintableJSON

Details

    Description

      When doing repair on a system with lots of mismatched ranges, the number of tables in L0 goes up dramatically, as correspondingly goes the number of tables referenced for a query. Latency increases dramatically in tandem.

      Eventually all the copied tables are compacted down in L0, then copied into L1 (which may be a very large copy), finally reducing the number of SSTables per query into the manageable range.

      It seems to me that the cleanest answer is to compact after streaming, then mark tables available rather than marking available when the file itself is complete.

      Attachments

        Issue Links

          Activity

            People

              scv119@gmail.com Chen Shen
              autocracy Jeff Ferland
              Chen Shen
              Votes:
              1 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated: