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

Cassandra fails to start with OOM after disk space problem occurred

Agile BoardAttach 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: Cannot Reproduce
    • 2.1.5
    • None
    • None
    • Normal

    Description

      It one point the Cassandra failed with
      org.apache.cassandra.io.FSWriteError: java.io.IOException: No space left on device

      Which seems pretty normal situation. But after the disk space was increased, Cassandra refused to start up again. The memory snapshot shows a big ArrayList of org.apache.cassandra.io.sstable.SSTableScanner is allocated, holding around 2.8Gb.
      It looks like the DB is corrupted, but we're not entirely sure.

      Attachments

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

          People

            Unassigned Unassigned Assign to me
            maximp Maxim Podkolzine
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment