[
https://issues.apache.org/jira/browse/CASSANDRA-16507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16507:
-----------------------------------------
Resolution: Invalid
Status: Resolved (was: Triage Needed)
Unfortunately I don't think anyone is going to invest effort into
troubleshooting modified source code. If you can show this happens when
mutations are dropped naturally or some other way it can be looked into.
> Node unreachable to each other with MUTATION message dropped
> ------------------------------------------------------------
>
> Key: CASSANDRA-16507
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16507
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
> Reporter: Yixin Zou
> Priority: Normal
>
> Cluster setup: Ubuntu 18.04-LTS, cassandra-3.11.10. One DC, 3 nodes, 2
> replication factor;
> Using an injector to filter and drop MUTATION message between one node and
> the other two (drop MUTATION messages sent from node 1 to node 2, 3 and drop
> MUTATION messages sent from node 2, 3 to node 1). At the same time, inserted
> same key, different values on node 1 and node 2. When insertion happened,
> MUTATION message drops were caught on both node 1 and node2. Then we observed
> the different values for that key on two nodes and observed all three nodes
> disconnected from each other.
>
> {code:java}
> ./nodetool describecluster
> /Cluster Information:Cluster Information:
> Name: Test Cluster Snitch:
> org.apache.cassandra.locator.GossipingPropertyFileSnitch
> DynamicEndPointSnitch: enabled Partitioner:
> org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions: UNREACHABLE: [10.0.1.8, 10.0.1.7, 10.0.1.9]
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
