Configuring JVM options in LCM
Configure JVM options from within Lifecycle Manager.
For more information on JVM, see Tuning Java resources.
Procedure
What's next
- Run a configure job to apply the config profile changes.
Simplify deploying and configuring DataStax Enterprise clusters with Lifecycle Manager.
Define centrally-managed configuration profiles to enforce uniform configuration at the cluster, datacenter, or node level.
Edit a configuration profile. If the configuration profile is already in use, run a configure job to apply the changes.
Configure JVM options from within Lifecycle Manager.
Simplify deploying and configuring DataStax Enterprise clusters with Lifecycle Manager.
An introduction to Lifecycle Manager (LCM) for provisioning DataStax Enterprise (DSE) clusters and centrally managing configurations. Simplify deploying and configuring DataStax Enterprise clusters with Lifecycle Manager.
Create and manage the DataStax Enterprise cluster topology model in the Clusters workspace of Lifecycle Manager. Run install and configure jobs at the cluster, datacenter, or node level.
View a summary and drill into details of install, configure, and import jobs in Lifecycle Manager. Monitor the progress of running jobs. Troubleshoot failed and abort idle jobs.
Repositories use predefined credentials for automatically downloading Debian or RPM packages from the DataStax Enterprise repository or from a private repository that is an internal mirror of the DataStax repository.
SSH credentials allow securely connecting to machines without repeatedly entering credentials for each DataStax Enterprise install, configure, or import job. Define SSH credentials for cluster, datacenter, or node levels.
Define centrally-managed configuration profiles to enforce uniform configuration at the cluster, datacenter, or node level.
Define the required configuration profiles to prevent configuration drift for DataStax Enterprise clusters. A configuration profile enforces uniform configuration at the cluster, datacenter, or node level.
The items below are common known issues that you might encounter when configuring DataStax Enterprise clusters in Lifecycle Manager (LCM). Wherever possible, workarounds are included.
Authentication for DataStax Enterprise clusters is enabled by default in a Lifecycle Manager configuration profile.
Add a configuration profile that defines the configuration for DataStax Enterprise clusters. The config profile informs Lifecycle Manager which supported version of DataStax Enterprise to install, configure, and manage.
Edit a configuration profile. If the configuration profile is already in use, run a configure job to apply the changes.
Configure SSL/TLS for a DSE cluster using Lifecycle Manager Config Profile. This is the recommended procedure for a production environment. Follow these steps to enable node-to-node and client-to-node encryption.
Configure Lifecycle Manager for DSE Graph workloads.
DSE Tiered Storage segregates hot and cold data. Configure the storage tier strategy and paths to each tier in an LCM config profile.
Enable row-level access control (RLAC) in LCM for DSE clusters that have tables with row-level permissions required for user access.
Configure a local or remote JMX connection to DSE using Lifecycle Manager.
Configure JVM options from within Lifecycle Manager.
Automatically manage Java installs and upgrades from within configuration profiles. Manage installs of JCE Policy files.
Configure an http or https proxy for expediting package downloads by way of caching, or for an environment where DataStax Enterprise clusters must be isolated offline from the internet.
Delete a configuration profile. Delete a config profile if it is obsolete or if you prefer a node or datacenter to inherit a config profile from its cluster.
Configuration options available in opscenterd.conf for Lifecycle Manager.
Configure JVM options from within Lifecycle Manager.
For more information on JVM, see Tuning Java resources.
-XX:MaxJavaStackTraceDepth=1000
-Dcassandra.max_queued_native_transport_requests=1024
© DataStax, Inc. All rights reserved. Updated: 2019-02-11
Build time: 2019-02-11 13:57:49.495DataStax, Titan, and TitanDB are registered trademark of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, 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.