Is your feature request related to a problem? Please describe.
I recently realized that my Cadence/Cassandra deployment was not truly HA, since the keyspaces cadence and cadence_visibility within Cassandra only had replication factors of 1. This meant that any time on of my three cassandra nodes went down, any reads would fail.
Describe the solution you'd like to see
A replication factor argument can be passed to cadence-cassandra-tool at the time of bootstrapping cadence. This is currently being done on this line.
The simplest solution, probably, would be to add the -rf flag to the call of cadence-cassandra-tool, and include the parameter's value in the helm values of the cadence chart. E.g.
Describe alternatives you've considered
There don't seem to be any alternatives to bootstrapping Cadence's keyspaces in Cassandra, save pre-deploying Cassandra and running the cadence-cassandra-tool create command manually.
Is your feature request related to a problem? Please describe. I recently realized that my Cadence/Cassandra deployment was not truly HA, since the keyspaces
cadence
andcadence_visibility
within Cassandra only had replication factors of 1. This meant that any time on of my three cassandra nodes went down, any reads would fail.Describe the solution you'd like to see A replication factor argument can be passed to
cadence-cassandra-tool
at the time of bootstrapping cadence. This is currently being done on this line.The simplest solution, probably, would be to add the
-rf
flag to the call ofcadence-cassandra-tool
, and include the parameter's value in the helm values of the cadence chart. E.g.Describe alternatives you've considered There don't seem to be any alternatives to bootstrapping Cadence's keyspaces in Cassandra, save pre-deploying Cassandra and running the
cadence-cassandra-tool create
command manually.