Ishaaq Chandy created CASSANDRA-5073:
----------------------------------------
Summary: Node movement results in excessive streaming
Key: CASSANDRA-5073
URL: https://issues.apache.org/jira/browse/CASSANDRA-5073
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.0.8
Reporter: Ishaaq Chandy
I have a 3-node cluster where almost all the keyspaces (other than Cassandra's
system and OpsCenter keyspaces) have a replication factor=3, this implies that
all nodes have all the data.
I needed to add a new node, so I proceeded to rearrange the tokens to make room
for it. My expectation was that node movement would be cheap before I added the
new node. Turns out it wasn't so, despite the fact that each node has all the
data, there was a ton of data being streamed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
