-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate Cassandra keyspace to NetworkTopologyStrategy #350
Comments
This seems to work when invoked by
Very weird since the same command seems to be working manually: ALTER KEYSPACE kong WITH REPLICATION = {'class' : 'NetworkTopologyStrategy', 'DC1' : 1}; |
See #543 for what needs to be done here. |
Implemented with #634. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should change the replication strategy of the Kong keyspace to
NetworkTopologyStrategy
as opposed to havingSimpleStrategy
to make it easier to scale a Cassandra cluster. From the Cassandra documentation:It means that
NetworkTopologyStrategy
can work pretty much in every scenario (including single-machine, or single-datacenter), whileSimpleStrategy
is more limited.Doing this should be as easy as executing:
This also brings another question: in a production environment I might be wanting to setup my own Cassandra cluster with some very specific settings, how do we prevent Kong migrations from being executed and reverting these settings?
The text was updated successfully, but these errors were encountered: