Customize configuration profile files
Configuration profiles 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. One configuration profile defines the following configuration files, which control various aspects of DSE clusters:
| Filename | Location for package installations | Location for tarball installations |
|---|---|---|
|
|
|
|
|
|
|
|
|
In your configuration profiles, you can customize the settings described on this page, which map to the configuration files used by DSE.
Edit a configuration profile
-
In the Lifecycle Manager menu, select Config Profiles.
-
Select the profile you want to edit or create a new one.
-
When viewing a configuration profile, select the file or section that you want to edit, and then modify the options as desired. For details about the available files and options, see Configuration profile files and options.
-
When you are finished customizing the settings, click Save to preserve your changes.
-
Run a configuration job to push the updated configuration profile and apply the changes at the cluster, datacenter, or node level, depending on the scope of the configuration profile.
Configuration profile files and options
- Cassandra
-
-
cassandra.yaml: All settings in this file can be edited. For all options, see cassandra.yaml configuration file. -
dse.yaml: All settings in this file can be edited. For all options, see dse.yaml configuration file.When you add a configuration profile, DSE authentication is enabled by default for all supported versions of DSE. The DSE Authenticator is enabled in
dse.yaml. For more information, see Configure DSE security using LCM. -
cassandra-env.sh: This file uses a restricted template system that exposes only common settings. Contact DataStax Support if you need additional options. For available options, see cassandra folder. -
logback.xml: This file uses a restricted template system that exposes only common settings. Contact DataStax Support if you need additional options. For all options, see Configure logging. -
jvm-server.options,jvm8-server.options,jvm11-server.options: These files use a restricted template system that exposes only common settings. Contact DataStax Support if you need additional options. For available options, see Configure JVM options for DataStax Enterprise using Lifecycle Manager.
-
- Spark
-
The following files are included in the Spark section. For more information about these files and options, see Configure Apache Spark and Configure Apache Spark logging options.
-
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
-
- Lifecycle Manager
-
-
Package Proxy: Provides options to accelerate package downloads or isolate DSE clusters offline from the internet.
-
Java Setup: Provides options to automatically manage JRE installs and JCE Policy files.
-
Files not managed by configuration profiles
The commitlog_archiving.properties file isn’t managed by Lifecycle Manager.
This file is used by the Backup Service to configure commit log archives and perform PIT restores. As a result, this file is managed by the Backup Service.
