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

Optimizing very small repair streams

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Consistency/Repair
    • Labels:
      None

      Description

      I often encountered repair scenarios, where a lot of tiny repair streams were created. This results in hundrets, thousands or even ten-thousands super small SSTables (some bytes to some kbytes).
      This puts a lot of pressure on compaction and may even lead to a crash due to too many open files - I also encountered this.

      What could help to avoid this:
      After CASSANDRA-12888 is resolved, a tiny stream (e.g. < 100kb) could be sent through the write path to be buffered by memtables instead of creating an SSTable each.

      Without CASSANDRA-12888 this would break incremental repairs.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                brstgt Benjamin Roth
              • Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated: