[
https://issues.apache.org/jira/browse/CASSANDRA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409764#comment-13409764
]
Pavel Yaskevich commented on CASSANDRA-4428:
--------------------------------------------
Have you tried to restart the node and execute update or dropping mt2 keyspace,
recreate with with initial values and update? I think that assertion from
CASSANDRA-4411 could have stalled the executor involved in saving schema to
disk.
> updating strategy_options has no effect
> ---------------------------------------
>
> Key: CASSANDRA-4428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4428
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.2
> Reporter: Christian Schnidrig
> Assignee: Pavel Yaskevich
>
> updating the strategy_options with cassandra-cli does not actually do
> anything:
> [default@unknown] use mt2;
> Authenticated to keyspace: mt2
> [default@mt2] update keyspace mt2 with placement_strategy =
> 'NetworkTopologyStrategy' and strategy_options = {OVH:1, FALKENSTEIN:1};
> 56c68393-fbcd-34be-b48b-59bd16e33c80
> Waiting for schema agreement...
> ... schemas agree across the cluster
> [default@mt2] show schema;
>
> create keyspace mt2
> with placement_strategy = 'NetworkTopologyStrategy'
> and strategy_options = {OVH : 2, FALKENSTEIN : 0}
> and durable_writes = true;
> the strategy_options were not updated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
