[
https://issues.apache.org/jira/browse/CASSANDRA-19445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851199#comment-17851199
]
Blake Eggleston commented on CASSANDRA-19445:
---------------------------------------------
So there are 3 processes that start a paxos repair. They're run as part of
{{{}nodetool repair{}}}, they're run as part of topology changes
(move/bootstrap/decommission), and they're run every 5 minutes as part of an
automatic cleanup process. I think that logging should remain at INFO for paxos
repairs that originate from repairs and topology changes , since these have
important implications for correctness. However I don't have any problems with
logging the auto cleanup process repair info at DEBUG, since they're just for
convenience / cleanup and also what's generating most of the noise you're
seeing.
> Cassandra 4.1.4 floods logs with "Completed 0 uncommitted paxos instances for"
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-19445
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19445
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Lightweight Transactions
> Reporter: Zbyszek Z
> Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.x
>
> Attachments: paxos-entry.txt, paxos-multiple.txt
>
>
> Hello,
> On our cluster logs are flooded with:
> {code:java}
> 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], {code}
> I cannot find anything in doc regarding this longline. Also this are huge log
> payloads that heavy flood system.log.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
