[ 
https://issues.apache.org/jira/browse/CASSANDRA-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825458#comment-17825458
 ] 

Brandon Williams commented on CASSANDRA-18335:
----------------------------------------------

This looks good to me, I don't think we need CI to push log levels down but I 
[smoke tested 
5.0|https://app.circleci.com/pipelines/github/driftx/cassandra/1504/workflows/9ab0975e-e8a1-4783-b4f8-201b22d3e3e8]
 just to make sure no tests were looking for these. Nothing there looks 
relevant, I'm +1.

bq. Also, I wasn't sure where to add the CHANGES.txt line for the 4.0 and 4.1 
PRs.

In general I would recommend that CHANGES not be addressed in PRs, since this 
will almost always later conflict for the committer, who will know where to put 
those lines anyway.

> Push LocalSessions info logs to debug
> -------------------------------------
>
>                 Key: CASSANDRA-18335
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18335
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Consistency/Repair
>            Reporter: Brandon Williams
>            Assignee: Arun Ganesh
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x, 5.x
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I don't think these are particularly useful to have at info, but the impetus 
> for this ticket is specifically [this 
> message|https://github.com/apache/cassandra/blob/cassandra-4.0/src/java/org/apache/cassandra/repair/consistent/LocalSessions.java#L456]
>  during automatic cleanup about skipping deleting sessions that seems to 
> confuse or alarm people.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to