apache/cassandra · warning

{} parameters have been deprecated. They have new names and/

Error message

{} parameters have been deprecated. They have new names and/or value format; For more information, please refer to NEWS.txt

What it means

Cassandra's YamlConfigurationLoader warns when cassandra.yaml contains parameters that have been renamed or had their value format changed between releases. The deprecated names are still mapped internally, but operators should migrate to the new names. The authoritative list of renames is in NEWS.txt for the target version.

Source

Thrown at src/java/org/apache/cassandra/config/YamlConfigurationLoader.java:563

                    root = null;
                    break;
                }
                root = root == null ? prop : Properties.andThen(root, prop);
                type = root.getType();
            }
            return root != null ? root : new MissingProperty(name);
        }

        public void check() throws ConfigurationException
        {
            if (!nullProperties.isEmpty())
                throw new ConfigurationException("Invalid yaml. Those properties " + nullProperties + " are not valid", false);

            if (!missingProperties.isEmpty())
                throw new ConfigurationException("Invalid yaml. Please remove properties " + missingProperties + " from your cassandra.yaml", false);

            if (!deprecationWarnings.isEmpty())
                logger.warn("{} parameters have been deprecated. They have new names and/or value format; For more information, please refer to NEWS.txt", deprecationWarnings);
        }
    }

    public static LoaderOptions getDefaultLoaderOptions()
    {
        LoaderOptions loaderOptions = new LoaderOptions();
        loaderOptions.setCodePointLimit(64 * 1024 * 1024); // 64 MiB
        loaderOptions.setWarnOnDuplicateKeys(false);
        return loaderOptions;
    }
}

View on GitHub (pinned to 88fd0f6a0e)

Solutions

1. Check the logged list of deprecated parameters and rename each to its new name per NEWS.txt for your Cassandra version
2. Diff your cassandra.yaml against conf/cassandra.yaml shipped with the new version and adopt the current keys
3. Restart and confirm the warning no longer appears in the log

Example fix

// before (old yaml)
commitlog_sync_period_in_ms: 10000
// after (renamed per NEWS.txt)
commitlog_sync_period: 10000ms

// Before deploying cassandra.yaml, grep for known-removed keys
const REMOVED = ['commitlog_sync_period_in_ms','read_request_timeout_in_ms'];
const deprecated = REMOVED.filter(k => yamlText.includes(k));
if (deprecated.length) throw new Error('Deprecated yaml keys: ' + deprecated.join(','));

When it happens

Trigger: Starting Cassandra (or loading config via Config.load) with a cassandra.yaml that still lists pre-4.x property names (e.g. commitlog_sync_period_in_ms, endpoint_snitch formats, changed timeout keys) so PropertiesChecker flags them as deprecationWarnings.

Common situations: Upgrading Cassandra in place while carrying over an old cassandra.yaml; copying a yaml from an older cluster; following outdated tutorials or Helm charts with legacy config keys.

Understand the failure class

Background: "is deprecated and will be removed" — deprecation warnings for old API names, keywords, and options, and how to migrate before the removal release — this error's family across 29 libraries.

Related errors

• Invalid yaml. Please remove properties <missingProperties> f
• memtable_cleanup_threshold has been deprecated and should be
• use_deterministic_table_id is no longer supported and should
• Invalid data rate: ${value} Accepted units: MiB/s, KiB/s, B/
• Invalid data rate: ${value}. It shouldn't be more than ${max

AI-assisted analysis of apache/cassandra@88fd0f6a0e (2026-09-10). Data as JSON: /api/errors/291978aa3639b84a. Report an issue: GitHub.