Customizing configuration profile files

About this task

Define configuration profiles to specify how DataStax Enterprise (DSE) will be configured. A configuration profile enforces uniform configuration at the cluster, datacenter, or node level.

Each configuration profile is specific to a supported version of DSE. A configuration profile is composed of multiple configuration files for configuring features of DSE clusters.

Configuration profiles allow customizing settings for the following DSE Configuration profile files.

Configuration files
Filename Location dependent on the type of installation

cassandra-env.sh

  • Package installations: /etc/dse/cassandra/cassandra-env.sh

  • Tarball installations: installation_location/resources/cassandra/conf/cassandra-env.sh

cassandra.yaml

  • Package installations: /etc/dse/cassandra/cassandra.yaml

  • Tarball installations: installation_location/resources/cassandra/conf/cassandra.yaml

dse.yaml

  • Package installations: /etc/opscenter/clusters/cluster_name.conf

  • Tarball installations: install_location/conf/clusters/cluster_name.conf

Procedure

  1. From the Lifecycle Manager side menu, click Config Profiles.

  2. Under Config Profile, click the file to customize.

    Configurable options for the file display in the main content pane.

  3. Enter a value or make a selection for the option you want to customize.

  4. When finished customizing options, click Save to apply the changes.

  5. Run a configuration job to push configuration profile updates and apply them at the cluster, datacenter, or node level.

Configuration profile files

Cassandra section

When you add a configuration profile, DSE authentication is enabled by default for all supported versions of DSE. DSE Authenticator is enabled in dse.yaml. For more information, see Managing DSE Security using LCM.

Every configuration option in cassandra.yaml and dse.yaml is editable, while other configuration files use a template system that exposes only frequently used settings. Contact DataStax Support to request additional configuration options.

Spark section

  • spark-alwayson-sql.conf

  • logback-sparkR.xml

  • dse-spark-env.sh

  • logback-spark.xml

  • spark-defaults.conf

  • spark-env.sh

  • logback-spark-executor.xml

  • logback-spark-server.xml

  • hive-site.xml

  • spark-daemon-defaults.conf

For more information about Spark, see Configuring Spark and Configuring Spark logging options.

Lifecycle Manager section

  • Package Proxy: Accelerate package downloads or isolate DSE clusters offline from the internet.

  • Java Setup: Automatically manages JRE installs and JCE Policy files.

A configuration file explicitly not managed at this time by Lifecycle Manager is commitlog_archiving.properties, which is used for configuring commit log archive and PIT restore for the Backup Service. This file is managed instead from within the Backup Service.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com