[
https://issues.apache.org/jira/browse/CASSANDRA-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17472:
--------------------------------------
Fix Version/s: 4.1
Source Control Link:
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=fbd6b047915d9810bf5e3131ba11c9374b3834a3
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed. Thanks [~brandon.williams]
> 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
> Fix For: 4.1
>
>
> 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]
