[CASSANDRA-17472] On CFS.flushLargestMemtable, log candidate at info instead of debug

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.1-alpha1, 4.1
• Component/s: Local/Memtable
• Change Category: Operability
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=fbd6b047915d9810bf5e3131ba11c9374b3834a3

Test and Documentation Plan

No new testing or documentation needed.

• Assignee: Josh McKenzie
• Reporter: Josh McKenzie

Authors

Josh McKenzie

Reviewers

Brandon Williams

• Created: 22/Mar/22 16:39
• Updated: 27/May/22 19:25
• Resolved: 22/Mar/22 19:20

Description

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.