Russell Alexander Spitzer created CASSANDRA-6210:
----------------------------------------------------
Summary: Repair hangs when a new datacenter is added to a cluster
Key: CASSANDRA-6210
URL: https://issues.apache.org/jira/browse/CASSANDRA-6210
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: Amazon Ec2
2 M1.large nodes
Reporter: Russell Alexander Spitzer
Attempting to add a new datacenter to a cluster seems to cause repair
operations to break. I've been reproducing this with 20~ node clusters but can
get it to reliably occur on 2 node setups.
{code}
##Basic Steps to reproduce
#Node 1 is started using GossipingPropertyFileSnitch as dc1
#Cassandra-stress is used to insert a minimal amount of data
$CASSANDRA_STRESS -t 100 -R
org.apache.cassandra.locator.NetworkTopologyStrategy --num-keys=1000
--columns=10 --consistency-level=LOCAL_QUORUM --average-size-values -
-compaction-strategy='LeveledCompactionStrategy' -O dc1:1
--operation=COUNTER_ADD
#Alter "Keyspace1"
ALTER KEYSPACE "Keyspace1" WITH replication = {'class':
'NetworkTopologyStrategy', 'dc1': 1 , 'dc2': 1 };
#Add node 2 using GossipingPropertyFileSnitch as dc2
run repair on node 1
run repair on node 2
{code}
The repair task on node 1 never completes and while there are no exceptions in
the logs of node1, netstat reports the following repair tasks having never
completed
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
