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

Avoid index segment stitching in RAM which lead to OOM on big SSTable files

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 3.5
    • Legacy/CQL
    • C* 3.4

    • Normal
    • 3.4

    Description

      13 bare metal machines

      • 6 cores CPU (12 HT)
      • 64Gb RAM
      • 4 SSD in RAID0

      JVM settings:

      • G1 GC
      • Xms32G, Xmx32G

      Data set:

      • ≈ 100Gb/per node
      • 1.3 Tb cluster-wide
      • ≈ 20Gb for all SASI indices

      C* settings:

      • concurrent_compactors: 1
      • compaction_throughput_mb_per_sec: 256
      • memtable_heap_space_in_mb: 2048
      • memtable_offheap_space_in_mb: 2048

      I created 9 SASI indices

      • 8 indices with text field, NonTokenizingAnalyser, PREFIX mode, case-insensitive
      • 1 index with numeric field, SPARSE mode

      After a while, the nodes just gone OOM.

      I attach log files. You can see a lot of GC happening while index segments are flush to disk. At some point the node OOM ...

      /cc Pavel Yaskevich

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jwest Jordan West Assign to me
            doanduyhai DuyHai Doan
            Jordan West
            Pavel Yaskevich
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment