Customizing configuration profile files

Customize options for files that comprise an LCM configuration profile.

Define the required configuration profiles to prevent configuration drift for DataStax Enterprise (DSE) clusters. 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 configuration files.

Note: The data (cluster topology, configuration profiles, credentials, repositories, job history, and so forth) for Lifecycle Manager is stored in the lcm.db database. Your organization is responsible for backing up the lcm.db database. You must also configure failover to mirror the lcm.db database.

lcm.db

The location of the Lifecycle Manager database lcm.db depends on the type of installation:
  • Package installations: /var/lib/opscenter/lcm.db
  • Tarball installations: install_location/lcm.db

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:
    Note: 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 DSE version 5.0 and later. 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:
    • 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.
    Note: 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.