Generally a "new default" is created by changing the default value used when decoding the config that is used in the absence of the value- not changing a config variable in a shipped configuration file.
This isn't an issue with this project but it's an issue with ScyllaDB's communication with downstream consumers/orchestrators, such as this ansible role.
Generally a "new default" is created by changing the default value used when decoding the config that is used in the absence of the value- not changing a config variable in a shipped configuration file.
This isn't an issue with this project but it's an issue with ScyllaDB's communication with downstream consumers/orchestrators, such as this ansible role.
https://www.scylladb.com/2023/05/04/scylladbs-path-to-strong-consistency-a-new-milestone/