• Glossary
  • Support
  • Downloads
  • DataStax Home
Get Live Help
Expand All
Collapse All

DataStax Enterprise Installation Guide

    • Installing DSE 6.8
      • Which install method should I use?
      • Install on a single node
      • Installing supporting software
      • Installing a cluster using Lifecycle Manager 6.8
      • Installing from the Yum package
      • RedHat systemd configuration
      • Installing from the Debian package
      • Install from the tarball on any Linux distribution
      • Installing patch releases
      • Installing on cloud providers
      • Installing on Docker
      • Uninstalling DSE
      • Default DSE file locations
        • Package installations
        • Tarball installations
    • Installing DSE 6.8 Tools
      • Installing CQLSH
      • Installing DataStax Studio 6.8
      • Installing DSE Graph Loader
      • Installing DataStax Bulk Loader
      • Installing DataStax Apache Kafka Connector
    • Installing DSE OpsCenter 6.8
      • Installing from the RPM package
      • Installing from the Debian package
      • Installing from the tarball on any Linux distribution
      • Installing on Docker
      • Uninstalling OpsCenter
      • Installing DataStax Agents 6.8
        • Installing DataStax Agents automatically
        • Installing DataStax Agents manually
          • From the RPM package
          • From the Debian package
          • From a tarball
        • Setting Agent permissions to run as the DSE user
        • Configuring JAVA_HOME
  • DataStax Enterprise Installation Guide
  • Installing DSE 6.8
  • RedHat systemd configuration

RedHat systemd configuration

DSE versions 6.8.2 and higher support installation using systemd for RHEL-based and compatible systems.

The following units are installed in /usr/lib/systemd/system:

  • dse.target: starts DSE nodes

  • dse-shutdown.target: stops DSE nodes

In addition, a dse@.service template is installed into /usr/share/dse/templates and serves as a template unit for all DSE node instances running on the host OS under the cassandra user. That template is used by the dse add-node command and the /usr/share/dse/tools/dse-convert-to-systemd helper script.

Once dse.target is enabled, the dse add-node command creates and enables systemd service for new nodes, and also creates init.d scripts to redirect lifecycle commands to systemctl.

About this task

By default, systemd units are not enabled. Old init.d scripts remain in effect.

On systems that have systemd, the old init.d services can still be manipulated usiing systemd commands, for instance, systemctl start dse.

Procedure

  1. To enable DSE systemd units:

  2. Stop the DSE init.d service:

    sudo service dse stop
  3. Enable dse.target:

    sudo systemctl enable dse.target

    After dse.target is enabled, DSE nodes automatically start as part of the multi-user target on each reboot.

  4. On each node run:

    sudo /usr/share/dse/tools/dse-convert-to-systemd full-node-id

    The node address, full-node-id must be the full node ID including the dse- prefix. The default node ID if no other nodes are configured is dse.

    /usr/share/dse/tools/dse-convert-to-systemd dse-node1

    The dse-convert-tosystemd script makes the following changes:

    • Creates and enables systemd units for DSE nodes in /etc/systemd/system/.

    • Modifies the DSE init.d script to redirect lifecycle commands to systemctl.

Next Steps

DSE systemd operations include:

  • Start all DSE nodes:

    systemctl start dse.target
  • Stop all DSE nodes:

    systemctl start dse-shutdown.target
  • Start one DSE node:

    systemctl start full-node-id
  • Stop one DSE node:

    systemctl stop full-node-id

The node address, full-node-id must be the full node ID including the dse- prefix. The default node ID if no other nodes are configured is dse.

The default start timeout is 10 minutes and the default stop timeout is 30 seconds. Those values can be adjusted by editing the corresponding unit files.

Installing from the Yum package Installing from the Debian package

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

© DataStax | Privacy policy | Terms of use

DataStax, Titan, and TitanDB are registered trademarks 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 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.

landing_page landingpage