Lifecycle Manager configuration known issues and limitations
The items below are common known issues that might occur when configuring DataStax Enterprise clusters in Lifecycle Manager (LCM). Wherever possible, workarounds are included.
Encrypted DSE configuration values
config_encryption_active
is true
) on a DSE
cluster, you must disable data encryption before using LCM to configure DSE
clusters. To enable and disable configuration encryption:- DSE - Encrypting configuration file properties
- OpsCenter - Activating configuration encryption
Authentication scheme limitations
Internal authentication must be the primary authentication scheme. See Native transport authentication schemes and limitations in LCM for complete details.
DSE Graph properties (DSE 5.0.1+ only)
DSE Graph configuration in dse.yaml, which is configurable
through LCM Config Profiles. All Graph properties in dse.yaml
can be managed through the LCM UI with the exception of
gremlin_server.serializers
and
gremlin_server.scriptEngines
. If you are using LCM and need to
customize these properties, be sure to leverage the LCM API to make the changes. Future changes to the
Config Profile using the LCM UI will retain properties set through the API.