[ 
https://issues.apache.org/jira/browse/CASSANDRA-17159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Caleb Rackliffe updated CASSANDRA-17159:
----------------------------------------
    Test and Documentation Plan: 
- manual verification of logging output
- new in-jvm unit tests
                         Status: Patch Available  (was: In Progress)

patch: https://github.com/apache/cassandra/pull/1329
CircleCI: 
https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-17159

See [PR notes|https://github.com/apache/cassandra/pull/1329#issue-783181256].

> 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
>
>
> 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]

Reply via email to