You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2022/03/22 16:45:00 UTC
[jira] [Updated] (CASSANDRA-17472) On CFS.flushLargestMemtable, log candidate at info instead of debug
[ https://issues.apache.org/jira/browse/CASSANDRA-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh McKenzie updated CASSANDRA-17472:
--------------------------------------
Test and Documentation Plan: No new testing or documentation needed.
Status: Patch Available (was: Open)
> On CFS.flushLargestMemtable, log candidate at info instead of debug
> -------------------------------------------------------------------
>
> Key: CASSANDRA-17472
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17472
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Memtable
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
>
> When flushing the largest memtable in {{{}ColumnFamilyStore.flushLargestMemtable{}}}, we should log at info that a memtable was flushed due to this case rather than at debug. We don't expect this to trigger often and this information is useful for operators and shouldn't require elevated logging to see it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org