[ https://issues.apache.org/jira/browse/CASSANDRA-18753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821797#comment-17821797 ]
Ekaterina Dimitrova edited comment on CASSANDRA-18753 at 2/28/24 6:01 PM: -------------------------------------------------------------------------- [~blambov] , do we want to enable paxos v2 here by default? Considering that we have a few failures also presented in 4.1, and that the configuration to enable it is considered advanced and not even mentioned in default Cassandra.yaml for those reasons, I think we might still want to not enable it by default in the new config file for now. The Paxos v2 failures discovered here also exist in 4.1; I just marked them as 5.0 non-blockers for now. was (Author: e.dimitrova): [~blambov] , do we want to enable paxos v2 here by default? Considering that we have a few failures also presented in 4.1 and that the configuration to enable it is considered advanced and not even mentioned in default cassandra.yaml for those reasons, I think we might want to still not enable it by default in the new config file for now. > Add an optimized default configuration to tests and make it available for new > users > ----------------------------------------------------------------------------------- > > Key: CASSANDRA-18753 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18753 > Project: Cassandra > Issue Type: Improvement > Components: Packaging > Reporter: Branimir Lambov > Assignee: Branimir Lambov > Priority: Urgent > Fix For: 5.0-rc, 5.x > > Attachments: > CCM_Add_support_for_specifying_the_name_of_the_file_to_use_as_cassandra_YAML_.patch, > > DTEST_Add_support_for_specifying_the_name_of_the_file_to_use_as_cassandra_YAML_.patch > > Time Spent: 11h > Remaining Estimate: 0h > > We currently offer only one sample configuration file with Cassandra, and > that file is deliberately configured to disable all new functionality and > incompatible improvements. This works well for legacy users that want to have > a painless upgrade, but is a very bad choice for new users, or anyone wanting > to make comparisons between Cassandra versions or between Cassandra and other > databases. > We offer very little indication, in the database packaging itself, that there > are well-tested configuration choices that can solve known problems and > dramatically improve performance. This is guaranteed to paint the database in > a worse light than it deserves, and will very likely hurt adoption. > We should find a way to offer a very easy way of choosing between "optimized" > and "compatible" defaults. At minimal, we could provide alternate yaml files. > Alternatively, we could build on the {{storage_compatibility_mode}} concept > to grow it into a setting that not only enables/disables certain settings, > but also changes their default values. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org