[
https://issues.apache.org/jira/browse/CASSANDRA-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112384#comment-13112384
]
Vijay commented on CASSANDRA-3238:
----------------------------------
Steps to reproduce:
I think it is a generic problem when switching from simple strategy to NTS...
Connect your clients to the server and start inserting ur data with SS, then
without stopping the clients update to NTS and you will see the reads will
still go across and restart of the nodes will fix it... all the issues
mentioned seems to be related to that. I am still trying to find the root
cause, fix will be soon...
> Issue with multi region ec2 and replication updates
> ---------------------------------------------------
>
> Key: CASSANDRA-3238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3238
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Nick Bailey
> Assignee: Vijay
> Fix For: 1.0.0
>
>
> Using the Ec2MultiRegionSnitch and updating replication settings for a
> keyspace seems to cause some issues that require a rolling restart to fix.
> The following was observed when updating a keyspace from SimpleStrategy to
> NTS in a multi region environment:
> * All repairs would hang. Even repairs only against a keyspace that was not
> updated.
> * Reads at CL.ONE would start to go across region
> After a rolling restart of the cluster, repairs started working correctly
> again and reads stayed local to the region.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
