You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Joseph Lynch (Jira)" <ji...@apache.org> on 2019/09/06 15:29:00 UTC
[jira] [Created] (CASSANDRA-15306) Investigate why we are
allocating 8MiB chunks and reaching the maximum BufferPool size
Joseph Lynch created CASSANDRA-15306:
----------------------------------------
Summary: Investigate why we are allocating 8MiB chunks and reaching the maximum BufferPool size
Key: CASSANDRA-15306
URL: https://issues.apache.org/jira/browse/CASSANDRA-15306
Project: Cassandra
Issue Type: Bug
Components: Test/benchmark
Reporter: Joseph Lynch
While throwing some light traffic at {{4.0-alpha1}} I saw a lot of the following in the logs
{noformat}
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 {noformat}
This was with about 150 WPS against a LCS table containing 4kib data. 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).
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org