Jonathan Shook created CASSANDRA-11006:
------------------------------------------
Summary: Allow upgrades and installs to take modern defaults
Key: CASSANDRA-11006
URL: https://issues.apache.org/jira/browse/CASSANDRA-11006
Project: Cassandra
Issue Type: Improvement
Components: Configuration, Lifecycle, Packaging, Tools
Reporter: Jonathan Shook
See CASSANDRA-10425 for background.
We simply need to provide a way to install or upgrade C* on a system with
modern settings. Keeping the previous defaults has been the standard rule of
thumb to avoid surprises. This is a reasonable approach, but we haven't yet
provided an alternative for full upgrades with new default nor for more
appropriate installs of new systems. The number of previous defaults which may
need to be modified for a saner deployment has become a form of technical
baggage. Often, users will have to micro-manage basic settings to more
reasonable defaults for every single deployment, upgrade or not. This is
surprising.
For newer settings that would be more appropriate, we could force the user to
make a choice. If you are installing a new cluster or node, you may want the
modern defaults. If you are upgrading an existing node, you may still want the
modern defaults. If you are upgrading an existing node and have some very
carefully selected tunings for your hardware, then you may want to keep them.
Even then, they may be worse than the modern defaults, given version changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
