DataStax Enterprise 2.1 Documentation

Installing and Starting the DataStax Enterprise Binaries as Root

The quickest way to get up and running quickly with DataStax Enterprise (DSE) is to install the DataStax Enterprise tarball distribution and start a single-node analytics instance using root permissions or sudo. This installation creates files and directories outside of the install location. If you do not have root permissions or want to install as a user, see Installing and Starting the DataStax Enterprise Binaries as User.

DataStax Enterprise and OpsCenter Installation Steps

To install and start DataStax Enterprise:

  1. Check that Java is installed by running the following command in a terminal window:

    java -version
    

    Note

    Any version of Java is fine for installing an evaluation instance. For production deployments, see Installing Oracle JRE.

  2. Download the DataStax Enterprise package (required) and the OpsCenter package (optional) to your home directory. Substitute <username>:<password> with your login credentials.

    $ cd ~/
    $ curl -OL  http://<username>:<password>@downloads.datastax.com/enterprise/dse.tar.gz
    $ curl -OL  http://<username>:<password>@downloads.datastax.com/enterprise/opscenter.tar.gz
    
  3. Unpack the distributions:

    $ tar -xzvf dse.tar.gz
    $ tar -xzvf opscenter.tar.gz
    $ rm *.tar.gz
    
  4. Go to the install directory. For example:

    cd dse-2.1
    
  5. Start DataStax Enterprise (as an Analytics node - for running the Portfolio Manager Demo):

    $ sudo bin/dse cassandra -t
    

    where cassandra starts the Cassandra process plus CassandraFS and the -t option starts the Hadoop JobTracker and TaskTracker processes.

    Note

    When Cassandra loads, you may notice a message that MX4J will not load and that mx4j-tools.jar is not in the classpath. You can ignore this message. MX4j provides an HTML and HTTP interface to JMX and is not necessary to run Cassandra. DataStax recommends using OpsCenter. It has more monitoring capabilities than MX4J.

  6. Check that your cluster is up and running (from the install directory):

    $ bin/nodetool ring -h localhost
    

    ../../_images/nodetoolring21_dse.png