[CASSANDRA-19445] Cassandra 4.1.4 floods logs with "Completed 0 uncommitted paxos instances for"

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.1.6, 5.0-rc1, 5.1-alpha1
• Component/s: Feature/Lightweight Transactions
• Bug Category: Degradation - Resource Management
• Severity: Normal
• Complexity: Normal
• Discovered By: User Report
• Platform: All
• Since Version: 4.1.0

Source Control Link

https://github.com/apache/cassandra/commit/a17e4fc49768794adf471f35506647596f962ca1

Test and Documentation Plan

ci

• Assignee: Tommy Stendahl
• Reporter: Zbyszek Z

Authors

Tommy Stendahl

Reviewers

Blake Eggleston, Stefan Miklosovic

• Created: 27/Feb/24 14:44
• Updated: 10/Jul/24 11:57
• Resolved: 10/Jun/24 09:15

Description

Hello,

On our cluster logs are flooded with: 

INFO  [OptionalTasks:1] 2024-02-27 14:27:51,213 PaxosCleanupLocalCoordinator.java:185 - Completed 0 uncommitted paxos instances for XXXXXXXXX on ranges [(9210458530128018597,-9222146739399525061], (-9222146739399525061,-9174246180597321488], (-9174246180597321488,-9155837684527496840], (-9155837684527496840,-9148981328078890812], (-9148981328078890812,-9141853035919151700], (-9141853035919151700,-9138872620588476741], 

I cannot find anything in doc regarding this longline. Also this are huge log payloads that heavy flood system.log. 

Issue Links

• links to: GitHub Pull Request #3352
• links to: GitHub Pull Request #3353
• links to: GitHub Pull Request #3354