DataStax Enterprise 2.1 Documentation
Reference Information¶
Miscellaneous information about DataStax Enterprise.
- Locations of the Configuration Files
- Packaged Install Locations
- Binary Tarball Install Locations
- Configuring Firewall Port Access
- Starting a DataStax Enterprise Cluster
- Stopping DataStax Enterprise or Cassandra Nodes
- Installing glibc on OEL 6.x and later
Locations of the Configuration Files¶
The configuration files, such as cassandra.yaml, are located in the following directories:
- DataStax Enterprise packaged installs: /etc/dse/cassandra
- DataStax Enterprise binary installs: <install_location>/resources/cassandra/conf
Packaged Install Locations¶
The DataStax Enterprise CentOS/OEL/RHEL and Debian/Ubuntu packages are installed into the following directories:
Cassandra Directories
- /var/lib/cassandra (Cassandra and CassandraFS data directories)
- /var/log/cassandra
- /var/run/cassandra
- /usr/share/dse/cassandra (Cassandra environment settings)
- /usr/share/dse/cassandra/lib
- /usr/share/dse-demos (Portfolio, Solr, Sqoop)
- /usr/bin
- /usr/sbin
- /etc/dse/cassandra (Cassandra configuration files)
- /etc/init.d
- /etc/security/limits.d
- /etc/default/
Hadoop Directories
- /usr/share/dse/hadoop (Hadoop environment settings)
- /etc/dse/hadoop (Hadoop configuration files)
Hive Directories
- /usr/share/dse/hive (Hive environment settings)
- /etc/dse/hive (Hive configuration files)
Mahout Directories
- /usr/share/dse/mahout (Mahout properties files)
- /etc/dse/mahout (Mahout JAR files)
Pig Directories
- /usr/share/dse/pig (Pig environment settings)
- /etc/dse/pig (Pig configuration files)
Solr Directories
- /usr/share/dse-demos (Search - Wikipedia demo)
Sqoop Directories
- /usr/share/dse/sqoop (Sqoop environment settings)
- /etc/dse/sqoop
- /usr/share/dse-demos (Sqoop demo)
Log4j Directories
- /etc/dse/log4j (log4j configuration file)
- /usr/share/dse-demos (Log Search demo)
DataStax OpsCenter Directories
- /var/lib/opscenter (SSL certificates for encrypted agent/dashboard communications)
- /var/log/opscenter (log directory)
- /var/run/opscenter (runtime files)
- /usr/share/opscenter (JAR, agent, web application, and binary files)
- /etc/opscenter (configuration files)
- /etc/init.d (service startup script)
- /etc/security/limits.d (OpsCenter user limits)
Binary Tarball Install Locations¶
The tar installation creates the following directories in the <install_location> directory:
DataStax Enterprise Directories
- bin (DataStax Enterprise start scripts)
- demos (Portfolio Manager Demo)
- interface
- javadoc
- lib
- resources/cassandra/bin (Cassandra utilities)
- resources/cassandra/conf (Cassandra configuration files)
- resources/hadoop (Hadoop installation)
- resources/hive (Hive installation)
- resources/log4j-appender (log4j logging)
- resources/mahout (mahout installation)
- resources/pig (Pig installation)
- resources/solr (Solr installation)
- resources/sqoop (Sqoop installation)
Configuring Firewall Port Access¶
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.
| Port | Description |
|---|---|
| Public Facing Ports | |
| 22 | SSH (default) |
| 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 |
| OpsCenter Specific | |
| 8888 | OpsCenter website port |
| Intranode Ports | |
| Cassandra Specific | |
| 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 |
| OpsCenter Specific | |
| 50031 | OpsCenter HTTP proxy for Job Tracker |
| 61620 | OpsCenter intra-node monitoring port |
| 61621 | OpsCenter agent ports |
Starting a DataStax Enterprise Cluster¶
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.
Starting DataStax Enterprise as a Stand-Alone Process¶
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
Starting DataStax Enterprise as a Service¶
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:
- HADOOP_ENABLED=1 - Designates the node as DataStax Enterprise analytics and starts the Hadoop Job Tracker and Task Tracker services.
- SOLR_ENABLED=1 - Starts the node as DSE Enterprise Search. See Getting Starting with DSE Search.
Note
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.
Stopping DataStax Enterprise or Cassandra Nodes¶
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>
Installing glibc on OEL 6.x and later¶
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.
cd /etc/yum.repos.dDownload the public-yum-ol6.repo package from the repository.
wget http://public-yum.oracle.com/public-yum-ol6.repo
Check that glibc.i686 is ready for installation and install it.
yum list yum install glibc.i686