[jira] [Commented] (CASSANDRA-1285) Have a way to increase the replication factor
[
https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086985#comment-13086985 ] Jonathan Ellis commented on CASSANDRA-1285: --- You're probably using NetworkTopologyStrategy. replication_factor is ignored there. 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
[jira] [Commented] (CASSANDRA-1285) Have a way to increase the replication factor
[
https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086995#comment-13086995
]
Carl Heymann commented on CASSANDRA-1285:
-
Actually, I'm using SimpleStrategy:
{code}
[localcluster@unknown] describe keyspace LTS;
Keyspace: LTS:
Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
Options: [replication_factor:2]
...
{code}
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
[jira] [Commented] (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13087009#comment-13087009 ] Jonathan Ellis commented on CASSANDRA-1285: --- Then the first thing you should do is upgrade in case there is a bug in your version. P.S. a year-old ticket is the wrong place to discuss 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
[jira] [Commented] (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13087031#comment-13087031 ] Carl Heymann commented on CASSANDRA-1285: - OK, I tested with 0.8.4, and seems to be working there. I think I ran into CASSANDRA-2846 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
[jira] Commented: (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908542#action_12908542 ] Hudson commented on CASSANDRA-1285: --- Integrated in Cassandra #533 (See [https://hudson.apache.org/hudson/job/Cassandra/533/]) 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. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905820#action_12905820 ] Stu Hood commented on CASSANDRA-1285: - * The purge() and map() steps in UpdateColumnFamily.applyModels don't seem necessary, since CFMetaData.apply() doesn't allow you to change the keyspace, columnfamily or id * In UpdateKeyspace: Keyspace updated. Plese perform any manual operations * Direct Class.forName in system_update_keyspace can be replaced with FBUtilities.classForName Thanks! 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: v1-0001-thrift-changes.txt, v1-0002-UpdateKeyspace-migration.txt, v1-0003-UpdateColumn-family.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. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906057#action_12906057 ] Stu Hood commented on CASSANDRA-1285: - +1 for 0001-0004. Thanks! 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. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905511#action_12905511 ] Gary Dusbabek commented on CASSANDRA-1285: -- I should add that this patch just receives the updated values, records them, and then reloads the keyspaces/column families. Depending on what specifically changes, other operations must occur (repair, cleanup, etc). None of those operations are kicked off here. 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: v1-0001-thrift-changes.txt, v1-0002-UpdateKeyspace-migration.txt, v1-0003-UpdateColumn-family.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. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905703#action_12905703 ] Stu Hood commented on CASSANDRA-1285: - I'll take a look at this this evening. 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: v1-0001-thrift-changes.txt, v1-0002-UpdateKeyspace-migration.txt, v1-0003-UpdateColumn-family.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. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893230#action_12893230 ] Gary Dusbabek commented on CASSANDRA-1285: -- Is there any interest in making this a generic have a way to modify KS/CF properties ticket? Regardless, in the past there have been operations that needed to happen external from the change (cleanup or repair in the case of changing the RF). Should that still happen externally (keeps this ticket simple), or should those operations be invoked as part of changing the replication factor (this is complicated). 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.0 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. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1285) Have a way to increase the replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893269#action_12893269 ] Jonathan Ellis commented on CASSANDRA-1285: --- for 0.7, i would like a modify property X to value Y method, and leave everything else to be done manually a la 0.6. 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.0 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. - You can reply to this email to add a comment to the issue online.
