We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue keeps track of the need to add support for the "cassandra.force_3_0_protocol_version" property explained here https://docs.datastax.com/en/upgrade/doc/upgrade/datastax_enterprise/upgdDseMinor50x.html for updating from DSE 5.0.0-5.0.8 to 5.0.9 and later 5.0.x releases.
It looks like this also applies to Apache Cassandra, too: https://issues.apache.org/jira/browse/CASSANDRA-13004
Is templates/default/cassandra-env.sh.erb JVM_OPTS the right place for this?
The text was updated successfully, but these errors were encountered:
@rehevkor5 yes, we configure things such as cassandra.jmx.local.port there so I'd say it belongs there. Free free to submit a PR. Thank you!
cassandra.jmx.local.port
Sorry, something went wrong.
No branches or pull requests
This issue keeps track of the need to add support for the "cassandra.force_3_0_protocol_version" property explained here https://docs.datastax.com/en/upgrade/doc/upgrade/datastax_enterprise/upgdDseMinor50x.html for updating from DSE 5.0.0-5.0.8 to 5.0.9 and later 5.0.x releases.
It looks like this also applies to Apache Cassandra, too: https://issues.apache.org/jira/browse/CASSANDRA-13004
Is templates/default/cassandra-env.sh.erb JVM_OPTS the right place for this?
The text was updated successfully, but these errors were encountered: