[
https://issues.apache.org/jira/browse/CASSANDRA-21820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134108#comment-18134108
]
Dmitry Konstantinov commented on CASSANDRA-21820:
-------------------------------------------------
{code}
Where it ran: Cassandra-4.1-dtest-novnode #613, jdk8, split 36, agent
cassandra2. That agent has 8 CPUs and data on /dev/sda3. Both flaky attempts
failed the same way, on round 1's DROP COLUMNFAMILY ks.cf with node2 as
coordinator.
Timeline, attempt 2 (from the node logs on nightlies; attempt 1 looks the same):
┌───────────────┬────────────────────────────────────────────────────────────────────────────────────────────────┐
│ time │ what happened
│
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────┤
│ 22:17:37.38 │ node2 receives the DROP; the client's 10s timer starts
│
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────┤
│ 37.4 → 41.32 │ node2 drops the table locally (~4s), then pushes the change
to node1 and node3 │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────┤
│ 41.33 → 47.8+ │ node1 and node3 apply it; their logs end mid-flush at 47.59
and 47.84 when teardown kills them │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────┤
│ 47.38 │ client deadline passes → OperationTimedOut
│
{code}
> Flaky test: materialized_views_test.TestMaterializedViews.test_drop_mv
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-21820
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21820
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Dmitry Konstantinov
> Priority: Normal
>
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
