Quick Start Documentation
Installing DataStax Enterprise¶
(Back to start)This guide is now deprecated!¶
Use the new Getting started guide instead.
If you have trouble installing, see the full DataStax Enterprise installation documentation.
Choose your platform:
- Debian or Ubuntu (package install)
- CentOS, RHEL, or Oracle Linux (package install)
- All Linux distributions and Mac (binary tarball install)
Installing on Debian or Ubuntu
Before you can install, you must register with DataStax to get a username and password.
In a terminal window:
- Add the following to /etc/apt/sources.list.d/datastax.sources.list:
deb http://<username>:<password>@debian.datastax.com/enterprise stable main
- Add the following to /etc/apt/sources.list.d/cassandra.sources.list:
deb http://debian.datastax.com/community stable main
- Install DataStax Enterprise and OpsCenter:
curl -L http://debian.datastax.com/debian/repo_key | sudo apt-key add - sudo apt-get update sudo apt-get install dse-full opscenter
Install DataStax Community:
curl -L http://debian.datastax.com/debian/repo_key | sudo apt-key add - sudo apt-get update sudo apt-get install dsc12
Debian packages start the Cassandra service automatically.
- Start DataStax Enterprise:
sudo dse cassandra -t
-t starts Cassandra as a Hadoop (analytics) node.
- Verify that DataStax Enterprise is running:
nodetool ring -h localhost
- Verify that DataStax Community is running:
nodetool status
- (Optional) Install and set up OpsCenter.
Next steps
- Read the two minute overview.
- Run a demo: Portfolio | Hive | Mahout | Pig | Wikipedia (Solr) | Logging (Solr) | Sqoop.
- Read the complete DataStax Enterprise Documentation.
- Read the complete Cassandra Documentation.
Installing on CentOS, RHEL, or Oracle Linux
Before you can install, you must register with DataStax to get a username and password.
In a terminal window for both 32- and 64-bit systems:
- (RHEL 5.x/CentOS 5.x only) Make sure you have EPEL (Extra Packages for Enterprise Linux) installed:
rpm -Uvh http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
- Add a Yum repository for DataStax in /etc/yum.repos.d/datastax.repo:
[datastax] name= DataStax Repo for Apache Cassandra baseurl=http://<username>:<password>@rpm.datastax.com/enterprise enabled=1 gpgcheck=0
- Add a Yum repository for DataStax in /etc/yum.repos.d/datastax.repo:
[datastax] name= DataStax Repo for Apache Cassandra baseurl=http://<username>:<password>@rpm.datastax.com/community enabled=1 gpgcheck=0
- Install DataStax Enterprise and OpsCenter using Yum:
yum install dse-full opscenter
- Install DataStax Community and OpsCenter using Yum:
yum install dsc12
- Start DataStax Enterprise (as a single-node cluster):
sudo dse cassandra -t
-t starts Cassandra as a Hadoop (analytics) node.
- Start DataStax Community (as a single-node cluster):
sudo dsc cassandra
- Verify that DataStax Enterprise is running:
nodetool ring -h localhost
- Verify that DataStax Community is running:
nodetool status
- (Optional) Install and set up OpsCenter.
Next steps
- Read the two minute overview.
- Run a demo: Portfolio | Hive | Mahout | Pig | Wikipedia (Solr) | Logging (Solr) | Sqoop.
- Read the complete DataStax Enterprise Documentation.
- Read the complete Cassandra Documentation.
Installing the binaries on other Linux distributions or Mac
Before you can install, you must register with DataStax to get a username and password.
Prerequisites
- Ensure Python is installed.
- Ensure Java is installed.
Installing the binaries
In a terminal window:
- Download the tar archive:
curl -OL http://<username>:<password>@downloads.datastax.com/enterprise/dse.tar.gz
- Download the tar archive:
curl -OL http://downloads.datastax.com/community/dsc.tar.gz
- Unpack the tar archive for DataStax Enterprise:
tar -xzvf dse.tar.gz
- Unpack the tar archive for DataStax Community:
tar -xzvf dsc.tar.gz
- Go to the install directory:
cd dse-3.0.x
- Go to the install directory:
cd dsc-cassandra-1.2.x
- For instructions about installing without root permissions, click here.
- For instructions about installing without root permissions, click here.
- Create the data and log directories:
mkdir dse-data; cd dse-data mkdir data saved_caches commitlog
- Create the data and log directories:
mkdir cassandra-data; cd cassandra-data mkdir data saved_caches commitlog
- Edit <path_to_install>/resources/cassandra/conf/cassandra.yaml to include the settings:
initial_token: 0 data_file_directories: - <path_to_install>/dse-data/data commitlog_directory: <path_to_install>/dse-data/commitlog saved_caches_directory: <path_to_install>/dse-data/saved_caches
- Edit <path_to_install>/conf/cassandra.yaml to include the settings:
initial_token: 0 data_file_directories: - <path_to_install>/cassandra-data/data commitlog_directory: <path_to_install>/cassandra-data/commitlog saved_caches_directory: <path_to_install>/cassandra-data/saved_caches
- Edit <path_to_install>/resources/cassandra/conf/log4j-server.properties to include the settings:
log4j.appender.R.File= <path_to_install>/dse-data/system.log
- Edit <path_to_install>/conf/log4j-server.properties to include the settings:
log4j.appender.R.File= <path_to_install>/cassandra-data/system.log
- Start DataStax Enterprise as a Hadoop (analytics) node from the install directory:
sudo bin/dse cassandra -t
- Start DataStax Enterprise as a Hadoop (analytics) node from the install directory:
bin/dse cassandra -t
- Start DataStax Community from the install directory:
sudo bin/cassandra
- Start DataStax Community from the install directory:
bin/cassandra
- Verify that DataStax Enterprise is running:
bin/nodetool ring -h localhost
- Verify that DataStax Community is running:
bin/nodetool status
- (Optional) Set up OpsCenter for a single node.
Next steps
- Read the two minute overview.
- Run a demo: Portfolio | Hive | Mahout | Pig | Wikipedia (Solr) | Logging (Solr) | Sqoop.
- Read the complete DataStax Enterprise Documentation.
- Read the complete Cassandra Documentation.
Setting up OpsCenter for a single node
When you install OpsCenter from the tarball distribution, root permissions are not required.
Prerequisites
- Python 2.6+
- OpenSSL 0.9.8: CentOS 5.x, Debian, Mac OSX, Oracle Linux 5.5, RHEL 5.x, SUSE Enterprise 11.x, Ubuntu, and Windows.
- OpenSSL 1.0.0: CentOS 6.x, Oracle Linux 6.1, and RHEL 6.x
- sysstat: needed for the collection of I/O metrics)
Notes
Ubuntu 11.x and 12.x require OpenSSL 0.9.8, not the default OpenSSL. See Troubleshooting in the OpsCenter documentation.
You may need to set JAVA_HOME. For example: export JAVA_HOME=/usr/java/latest/jre1.6.0_38/
Installing the OpsCenter binary
Download the tarball distribution of OpsCenter from the either the DataStax website or use the curl command:
DataStax Community
$ curl -OL http://downloads.datastax.com/community/opscenter.tar.gz
DataStax Enterprise
$ curl -OL http://<username>:<password>@downloads.datastax.com/enterprise/opscenter.tar.gz
- Unpack the distribution.
$ tar -xzvf opscenter.tar.gz
Setting up OpsCenter and the OpsCenter agent
You need to configure OpsCenter to listen for client connections and tell the agent the IP address of the OpsCenter host.
- Add a symbolic link to the Oracle JRE installation for the keytool. For example:
sudo update-alternatives --install "/usr/bin/keytool" "keytool" "/usr/java/latest/jre1.6.0_38/bin/keytool" 1 - Edit the [webserver] interface in the opscenterd.conf file:
cd <path_to_opscenter>/opscenter-3.x.x/conf
[webserver] port = 8888 interface = 0.0.0.0Note: If you use 0.0.0.0, anyone can one view it. For better security, use your external IP (WhatIsMyIP).
- Set the host IP address for the agent:
$ cd ../agent $ bin/setup localhost
Note: If you are not using the same computer to install the agent, enter the IP address of the OpsCenter host.
Starting OpsCenter and the agent
- Start OpsCenter:
$ cd .. $ bin/opscenter
If you want to start in the foreground, use -f.
- Start the OpsCenter agent:
$ cd agent $ bin/opscenter-agent
- Launch OpsCenter from a browser using the following URL:
http://localhost:8888
- In the Welcome to DataStax OpsCenter dialog box:
- Click Use Existing Cluster.
- In the Cluster Hosts/IP field, enter localhost.
- Click Save Cluster.
The OpsCenter Dashboard is displayed.
Note: It takes a few minutes for data to start appearing.