[
https://issues.apache.org/jira/browse/CASSANDRA-17197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509008#comment-17509008
]
Andres de la Peña commented on CASSANDRA-17197:
-----------------------------------------------
It seems that the problem was that {{{}CQLTester{}}}'s asynchronous cleanup
task was messing with the tests, as we have already found while fixing other
flaky tests. That task produces an asynchronous flush of the tables created by
the test. Since those tables contain large collections, their asynchronous
flushing will emit diagnostic events that might be visible for the next tests.
I have modified the tests to immediately drop the tables at termination, so
there isn't anything for the async cleanup task. I have also disabled
autocompaction for the created tables, since that might be problematic too.
Here is CI doubling the number of iterations:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1485]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1384/workflows/93f9dee0-e2c8-4223-9b07-298d2f4a1ebe]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1384/workflows/d4fdc205-eed0-4e8a-babc-874602646fd6]|
> Diagnostic events for guardrails
> --------------------------------
>
> Key: CASSANDRA-17197
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17197
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Add diagnostic events for guardrails, so we can monitor when each type of
> guardrail is triggered.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
