[
https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086835#comment-13086835
]
Carl Heymann commented on CASSANDRA-1285:
-----------------------------------------
I see the issue is resolved. Is there any special procedure necessary to change
the replication factor? If I try to update as follows (on a keyspace with
RF=2), using the CLI:
{code}
update keyspace LTS with strategy_options=[{replication_factor:3}];
{code}
I don't see any change in RF reported with "describe keyspace LTS;" It remains
2. Adding the placement strategy into the update command doesn't make a
difference. If I run repair on all nodes (there are 3 nodes), I don't see any
changes either.
Is there a different way I can try to achieve this?
> Have a way to increase the replication factor
> ---------------------------------------------
>
> Key: CASSANDRA-1285
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1285
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Affects Versions: 0.7 beta 1
> Reporter: Arya Goudarzi
> Assignee: Gary Dusbabek
> Fix For: 0.7 beta 2
>
> Attachments: v2-0001-thrift-changes.txt,
> v2-0002-UpdateKeyspace-migration.txt, v2-0003-UpdateColumn-family.txt,
> v2-0004-avro-update-ks-and-cf-implementations.txt
>
>
> In 0.6 we were able to change the storage.conf and increase the replication
> factor and restart the server then repair the data across cluster to increase
> the replication factor for a keyspace. In 0.7 having moved away from
> storage.conf, it would be a good idea to have a method in api/jmx to alter
> keyspace so that replication factor could be changed as in 0.6.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
