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

Investigate why we are allocating 8MiB chunks and reaching the maximum BufferPool size

    XMLWordPrintableJSON

    Details

    • Platform:
      All
    • Impacts:
      None

      Description

      While throwing some light traffic at 4.0-alpha1 I saw a lot of the following in the logs

      INFO  [CompactionExecutor:8] 2019-09-06 11:40:31,419 NoSpamLogger.java:91 - Maximum memory usage reached (512.000MiB), cannot allocate chunk of 8.000MiB
      
      INFO  [CompactionExecutor:8] 2019-09-06 11:55:31,419 NoSpamLogger.java:91 - Maximum memory usage reached (512.000MiB), cannot allocate chunk of 8.000MiB
      
      INFO  [CompactionExecutor:15] 2019-09-06 12:10:31,419 NoSpamLogger.java:91 - Maximum memory usage reached (512.000MiB), cannot allocate chunk of 8.000MiB
      
      INFO  [CompactionExecutor:18] 2019-09-06 12:25:31,421 NoSpamLogger.java:91 - Maximum memory usage reached (512.000MiB), cannot allocate chunk of 8.000MiB 

      This was with about 150 WPS against a LCS table containing 4kib partitions. It seemed that compaction proceeded just fine but I don't remember seeing this in previous testing runs and I'd like to make sure it's not a bug (otherwise we may want to reduce the logging). 

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jolynch Joey Lynch
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: