[
https://issues.apache.org/jira/browse/CASSANDRA-17159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-17159:
----------------------------------------
Fix Version/s: 4.1
Source Control Link:
https://github.com/apache/cassandra/commit/33fd2dc817f56116af0b4b7d2cd5365ce52948d9
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as
https://github.com/apache/cassandra/commit/33fd2dc817f56116af0b4b7d2cd5365ce52948d9
Thanks for the review!
> Log read timeouts and unavailables at INFO via a no-spam logger
> ---------------------------------------------------------------
>
> Key: CASSANDRA-17159
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17159
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Logging
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 4.1, 4.x
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> We don’t have great logging visibility into timeouts and unavailables for
> reads and range reads. If we limit output to something like 1 per minute at
> INFO, we should be able to avoid spam but also have some record of what
> exactly failed. This could be especially helpful during node bounces and
> upgrades.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
