Hi team, I would like to bring to the attention of the community CASSANDRA-15234, standardise config and JVM parameters.
This is work we discussed back in Summer 2020 just before our first 4.0 Beta release. During the discussion we figured out that there is more than one option to do the job and not enough time to get user feedback and finish it so this was delayed post-4.0 And here I am, bringing it back to the table. This work’s goal is: - To standardize naming - that we did by agreeing to the form noun_verb - Provision of values with units while maintaining backward compatibility. Those two parts are more or less already done. More interesting is the third part - reorganizing the cassandra.yaml file. My personal approach was to split it into sections, done here <https://github.com/ekaterinadimitrova2/cassandra/blob/b4eebe080835da79d032f9314262c268b71172a8/conf/cassandra.yaml> . Another proposal is done by Benedict; grouping the config parameters. To make it clearer, he created a yaml <https://github.com/belliottsmith/cassandra/blob/5f80d1c0d38873b7a27dc137656d8b81f8e6bbd7/conf/cassandra_nocomment.yaml> with comments mostly stripped. In his version, there are basic settings for network, disk etc all grouped together, followed by operator tuneables mostly under limits within which we now have throughput, concurrency, capacity. This leads to settings for some features being kept separate (most notably for caching), but helps the operator understand what they have to play with for controlling resource consumption. I am interested to hear what people think about the two options or if anyone has another idea to share, open discussion. Thank you, Ekaterina
