Skip to content
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

Cassandra/Scylla replication factor and replication strategy must be provided and frozen when creating/deploying the cluster #316

Open
matt-mazzucato opened this issue Jun 30, 2020 · 0 comments
Labels
database This issue or pull request is about database (e.g. schema change, queries, support, etc...) discussion This issue needs to be investigated/discussed (it might be already fixed, invalid or duplicated)

Comments

@matt-mazzucato
Copy link
Collaborator

Astarte keyspace is created once housekeeping starts and cannot be further modified. This must be taken into account when considering both replication strategy and replication factor.
The following facts must be considered:

  • the naming of the env variables related to the replication strategy must reflect that their value is set only once at startup (e.g. prepend bootstrap or initial to env);
  • currently, only Simple Strategy is supported. Network Topology Strategy should be supported (or enforced);
  • a proper data structure should be defined in order to define replication strategy and replication factor env. A first proposal consists of two alternatives: (1) a properly formatted string, (2) a valid json object. Further alternatives can be discussed.

Related to the aforementioned points, on the operator's end, the following facts hold:

  • the replication strategy/factor should be defined as required in the crd;
  • an admission webhook might be employed to prevent the user from modifying the replication strategy/factor once the resource is created.
@matt-mazzucato matt-mazzucato added discussion This issue needs to be investigated/discussed (it might be already fixed, invalid or duplicated) blocking This issue or pull request blocks a release (e.g. API change, major bug) database This issue or pull request is about database (e.g. schema change, queries, support, etc...) labels Jun 30, 2020
@bettio bettio removed the blocking This issue or pull request blocks a release (e.g. API change, major bug) label Apr 16, 2021
@Annopaolo Annopaolo transferred this issue from astarte-platform/astarte Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database This issue or pull request is about database (e.g. schema change, queries, support, etc...) discussion This issue needs to be investigated/discussed (it might be already fixed, invalid or duplicated)
Projects
None yet
Development

No branches or pull requests

2 participants