Miscellaneous information about DataStax Enterprise.
The configuration files, such as cassandra.yaml, are located in the following directories:
The DataStax Enterprise CentOS/OEL/RHEL and Debian/Ubuntu packages are installed into the following directories:
DataStax OpsCenter Directories
The tar installation creates the following directories in the <install_location> directory:
DataStax Enterprise Directories
If you have a firewall running on the nodes in your Cassandra or DataStax Enterprise cluster, you must open up the following ports to allow communication between the nodes, including certain Cassandra ports. If this isn't done, when you start Cassandra (or Hadoop in DataStax Enterprise) on a node, the node will act as a standalone database server rather than joining the database cluster.
|Public Facing Ports|
|DataStax Enterprise Specific|
|8012||Hadoop Job Tracker client port|
|8983||Solr port and Demo applications website port (Portfolio, Search, Search log)|
|50030||Hadoop Job Tracker website port|
|50060||Hadoop Task Tracker website port|
|8888||OpsCenter website port|
|1024+||JMX reconnection/loopback ports|
|7000||Cassandra intra-node port|
|7199||Cassandra JMX monitoring port|
|9160||Cassandra client port|
|DataStax Enterprise Specific|
|9290||Hadoop Job Tracker Thrift port|
|50031||OpsCenter HTTP proxy for Job Tracker|
|61620||OpsCenter intra-node monitoring port|
|61621||OpsCenter agent ports|
After you have installed and configured DSE on one or more nodes, you are ready to start your cluster starting with the seed nodes. In a mixed-workload DSE cluster, you must start the analytics seed node first.
Packaged installations include startup scripts for running DSE as a service. Binary packages do not.
If running a mixed-workload cluster, determine which nodes to start as analytics, Cassandra, and search nodes. Begin with the seed nodes first - analytics seed node, followed by the Cassandra seed node - then start the remaining nodes in the cluster one at a time. For additional information, see Initializing Multiple Data Center Clusters on DataStax Enterprise.
To start DataStax Enterprise as a stand-alone process:
From the install directory:
Analytics node: bin/dse cassandra -t
Cassandra node: bin/dse cassandra
Solr node: bin/dse cassandra -s
To check that your ring is up and running (from the install directory):
$ bin/nodetool ring -h localhost
Packaged installations provide startup scripts in /etc/init.d for starting DSE as a service.
For mixed-workload clusters, nodes that are Cassandra-only can simply start the DSE service (skip step 1).
To start DataStax Enterprise as a service:
Edit the /etc/default/dse file, and then add the appropriate line to this file, depending on the type of node you want:
Using the SOLR_ENABLED and HADOOP_ENABLED options together to enable both search and Hadoop analytics on the same node is only recommended for development. In production environments each node should be used only for one or the other.
Start the DSE service:
sudo service dse start
To check if your cluster is up and running:
nodetool ring -h localhost
On RHEL and CentOS, the DSE service runs as a java process. On Debian and Ubuntu systems, the DSE service runs as a jsvc process.
To stop the service on a node:
sudo service <cassandra | dse> stop
To stop the stand-alone process on a node:
To stop a node, find the Cassandra or DataStax Enterprise Java process ID (PID) and kill the process using its PID number (using sudo if necessary). For example:
$ ps auwx | grep <cassandra | dse> $ kill <pid>
Oracle Enterprise Linux 6.x and later do not, by default, install the 32-bit versions of the glibc libraries. You need to install the libraries in order to install DataStax Enterprise.
To install glibc on OEL:
Make the yum.repos.d your current directory.
Download the public-yum-ol6.repo package from the repository.
Check that glibc.i686 is ready for installation and install it.
yum list yum install glibc.i686