[
https://issues.apache.org/jira/browse/CASSANDRA-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510745#comment-17510745
]
Josh McKenzie commented on CASSANDRA-17472:
-------------------------------------------
[PR|https://github.com/apache/cassandra/pull/1518]
[JDK8
CI|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/187/workflows/40d6f589-2ff2-48fd-b676-564ae2e29865]
[JDK11
CI|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/187/workflows/7a7da043-1728-4944-927d-4b7820986312]
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
