[
https://issues.apache.org/jira/browse/CASSANDRA-17160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471260#comment-17471260
]
Ekaterina Dimitrova commented on CASSANDRA-17160:
-------------------------------------------------
The following tickets were opened:
# CASSANDRA-17245 Some TableMetrics tests occasionally fail in a similar
fashion
# CASSANDRA-17244 Fix
org.apache.cassandra.distributed.test.trackwarnings.TombstoneCountWarningTest.failThresholdSinglePartition
I was wondering whether to open ticket also for
[this|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1354/testReport/org.apache.cassandra.io.sstable/CQLSSTableWriterTest/testDateType_2/]
failure but [CircleCI didn't fail
|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1265/workflows/b099d26c-860c-472d-bb95-2d166ba2b408]
1000 times so I will not do it for now but keep an eye if I see it again. (I
didn't find any historical data of other failures of this test)
> Emit warnings for deprecated parameters (changed names) only once
> -----------------------------------------------------------------
>
> Key: CASSANDRA-17160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17160
> Project: Cassandra
> Issue Type: Improvement
> Components: Build
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Low
> Fix For: 4.0.2, 4.1
>
>
> We added backward compatibility for two config parameters in CASSANDRA-17141
> to fix a bug but I realized that with the current setup, a warning for
> deprecated parameter can be logged more than once which is not needed and
> only introduces noise to the logs.
> I already fixed that in CASSANDRA-15234 where this would lead to a lot of
> warnings and it is easy to spot. I will backport the tiny fix here too in
> case we add more parameters, etc; to prevent the potential noise.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
