[
https://issues.apache.org/jira/browse/CASSANDRA-17972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631787#comment-17631787
]
Stefan Miklosovic commented on CASSANDRA-17972:
-----------------------------------------------
I am stopping progress on this. When one checks how waiting for a stopped node
is done for 3.0, it is done by waiting for one specific log line (e.g. take a
look into GossipTests). That seems to fix the flakiness to some extent. However
there are other instances when it is flaky / something races.
Branches in this ticket to work on are not going anywhere. The latest build
where it flakes on something else again is here (1)
(1)
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1560/workflows/eb790063-7c5d-4e4b-be65-5d8911dbb3d7/jobs/7159
> nodetool resetlocalschema does not sync schema
> ----------------------------------------------
>
> Key: CASSANDRA-17972
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17972
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Cameron Zemek
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Steps to reproduce:
> {code:java}
> $ ccm create -n 2 -v 3.11.13 -s resettest
> $ ccm node1 cqlsh -e "CREATE KEYSPACE test WITH replication =
> {'class':'NetworkTopologyStrategy', 'datacenter1': 2}"
> $ ccm node1 cqlsh -e "CREATE TABLE test.messages(id int primary key, message
> text)"
> $ ccm node1 nodetool describecluster
> Cluster Information:
> Name: resettest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1, 127.0.0.2]
> $ ccm node2 nodetool resetlocalschema
> $ ccm node2 cqlsh -e 'describe full schema'
> $ find ~/.ccm/resettest/node2/data0/system_schema/ -maxdepth 2 -type f
> $ ccm node2 nodetool describecluster
> Cluster Information:
> Name: resettest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1]
> 59adb24e-f3cd-3e02-97f0-5b395827453f: [127.0.0.2]
> $ ccm node2 stop
> $ ccm node2 start
> $ ccm node2 nodetool describecluster
> Cluster Information:
> Name: jpmctest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1, 127.0.0.2]
> {code}
> Its not resyncing the schema until after restarting the node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
