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

Node OOMs on commit log replay when starting up

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 1.2.11, 2.0.2
    • None
    • None
    • Normal

    Description

      After some activity on batchlogs and hints and CFs restarted nodes without finished draining. On startup it OOMs.

      Investigating it found, that memtables occupied all available RAM, because MeteredFlusher is started later in setup code, so memtables cannot flush.

      Fixed by starting metered flusher before commit log replay starts

      Attachments

        1. CassandraDaemon.txt
          2 kB
          Oleg Anastasyev

        Activity

          People

            m0nstermind Oleg Anastasyev
            m0nstermind Oleg Anastasyev
            Oleg Anastasyev
            Jonathan Ellis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: