About DSE
DataStax Enterprise delivers Apache Cassandra™ in a database platform that meets the performance and availability demands of Internet-of-Things (IoT), Web, and Mobile applications. It provides enterprises a secure, fast, always-on database that remains operationally simple when scaled in a single data center or across multiple data centers and clouds.
Upgrading
See the DataStax Upgrade Guide.
Installing
DataStax Enterprise installation methods include GUI or text mode, unattended command line or properties file, YUM and APT repository, and binary tarball.
Installer - GUI or Text mode
DataStax Enterprise production installation or upgrade on any Linux-based platform using a graphical or text interface.
Installer - unattended
Install DataStax Enterprise using the command line or properties file.
Other install methods
Installation using YUM or APT packages or binary tarball.
On cloud providers
Installation on Amazon EC2, CenturyLink, GoGrid, HP cloud, or Microsoft Azure.
Installing EPEL on RHEL OS 5.x
Install Extra Packages for Enterprise Linux on RHEL OS 5.x.
Installing glibc on Oracle Linux
To install DSE on Oracle Enterprise Linux 6.x and later, install the 32-bit versions of the glibc libraries.
Uninstalling
Launch the uninstaller in the installation directory to uninstall DataStax Enterprise and DataStax Agent.
Starting & stopping DSE
You can start and stop DataStax Enterprise as a service or stand-alone process.
Starting as a service
Starting the DataStax Enterprise service when DataStax Enterprise was installed from the DataStax Installer with the Services option or from a package.
Starting as a stand-alone process
Starting the DataStax Enterprise process when DataStax Enterprise was installed from the DataStax Installer with the No Services option or from a tarball.
Stopping a node
Stopping DataStax Enterprise and the DataStax Agent on a node.
Configuration
Information about configuring DataStax Enterprise.
dse.yaml
dse.yaml is the primary DataStax Enterprise configuration file.
Configuring and using virtual nodes (vnodes)
A description of virtual nodes (vnodes) and using them in different types of datacenters. Also steps for disabling vnodes.
File locations: Installer-Services and Package
Locations when installing from the DataStax All-in-One Installer with Services option or package installations.
File locations: Installer-No Services and Tarball
Locations when installing from the DataStax All-in-One Installer with No Services selected or tarball installations.
Configuring the Tomcat log location
Steps to change the location of the Tomcat server logs for DSE Search.
DSE Analytics
DataStax Enterprise analytics includes integration with Apache Spark, Shark, BYOH (bring your own Hadoop), and DSE Hadoop.
About DSE Analytics
DataStax Enterprise serves the analytics market with significant features for analyzing huge databases.
DSE Analytics and Search integration
DSE SearchAnalytics clusters can use DSE Search queries within DSE Analytics jobs.
About the Cassandra File System (CFS)
A Hive or Pig analytics job requires a Hadoop file system to function. For use with DSE Hadoop, DataStax Enterprise provides a replacement for the Hadoop Distributed File System (HDFS) called the Cassandra File System (CFS).
Configuring DSE Analytics
Guidelines and steps to configure DSE Analytics.
Analyzing data using Spark
Spark is the default mode when you start an analytics node in a packaged installation. Spark runs locally on each node.
Analyzing data using DSE Hadoop
You can run analytics on Cassandra data using Hadoop that is integrated into DataStax Enterprise. The Hadoop component in DataStax Enterprise enables analytics to be run across the DataStax Enterprise distributed, shared-nothing architecture.
Analyzing data using external Hadoop systems (BYOH)
DataStax Enterprise works with external Hadoop systems in a bring your own Hadoop (BYOH) model. Use BYOH when you want to run DSE with a separate Hadoop cluster, from a different vendor.
DSE Search
DataStax Enterprise Search (DSE Search) simplifies using search applications for data that is stored in a Cassandra database. DSE Search is an enterprise grade search solution that is scalable to work across multiple data centers and the cloud.
About DSE Search
DSE Search (DataStax Enterprise Search) simplifies using search applications for data that is stored in a Cassandra database. DSE Search is an enterprise grade search solution that is scalable to work across multiple datacenters and the cloud.
Starting and stopping DSE Search
The way you start a DSE Search node depends on the type of installation.
DSE Search architecture
An overview of DataStax Enterprise Search architecture.
Queries
DSE Search hooks into the Cassandra Command Line Interface (CLI), Cassandra Query Language (CQL) library, the cqlsh tool, existing Solr APIs, and Thrift APIs.
Schema and data modeling
Topics on how the Solr schema defines the relationship between data in a table and a Solr core.
Configuring DSE Search
DSE Search configuration includes configuring nodes, search components, threading, filter cache, indexing, and completing other configuration tasks.
Operations
You can run DSE Search on one or more nodes. Typical operations including configuration of nodes, policies, query routing, balancing loads, and communications.
Performance tuning
Tuning DSE Search in the event of performance degradation, high memory consumption, or other problems.
Update request processor and field transformer
Use the custom update request processor (URP) to extend the Solr URP. Use the field input/output transformer API as an option to the input/output transformer support in Solr.
Unsupported features for DSE Search
Unsupported Cassandra and Solr features for DSE Search.
DSE Search vs. Open source
Differences between DSE Search and Open Source Solr (OSS).
DSE Search tutorials and demos
Use the tutorials and demos to learn how to use DSE Search.
Troubleshooting
Take appropriate action to troubleshoot inconsistent query results, trace Solr HTTP requests, and use Mbeans.
DSE Advanced Security
DataStax Enterprise includes advanced data protection for enterprise-grade databases including LDAP authentication support, internal authentication, object permissions, encryption, Kerberos authentication, and data auditing.
About security management
An overview of DataStax Enterprise security.
Authenticating with Kerberos
DataStax Enterprise authentication with Kerberos protocol uses tickets to prove identity for nodes that communicate over non-secure networks.
Authenticating with LDAP
DataStax Enterprise supports LDAP authentication support for external LDAP services.
Encryption
DataStax Enterprise supports encryption for in-flight data and at-rest data.
Running cqlsh
Sample files are provided to help configure authentication for Kerberos, SSL, and Kerberos and SSL.
Configuring data auditing
Enable logging for the audit logger on the node that is set up for logging. Logs provide detailed audit trails of cluster activity.
Internal authentication
Internal authentication is based on Cassandra-controlled login accounts and passwords.
Managing object permissions
Use GRANT/REVOKE to grant or revoke permissions to access Cassandra data.
Configuring keyspace replication
The system_auth and dse_security keyspaces store security authentication and authorization information.
Configuring firewall ports
If a firewall runs on the nodes in the Cassandra or DataStax Enterprise cluster, open up ports to allow communication between the nodes.
DSE Management Services
DSE Management Services automatically handle administration and maintenance tasks and assist with overall database cluster management.
Performance Service
The DataStax Enterprise Performance Service automatically collects and organizes performance diagnostic information into a set of data dictionary tables that can be queried with CQL.
Capacity Service
Automatically collects data about a cluster's operations, including Cassandra specific and platform specific (for example, disk metrics, network metrics), at both the node and column-family level (where applicable). Use OpsCenter to manage and perform trend analysis.
Repair Service
The Repair Service is designed to automatically keep data synchronized across a cluster. You can manage the Repair Service with OpsCenter or by using the command line.
DSE In-Memory
DataStax Enterprise includes DSE In-Memory for storing data to and accessing data exclusively from memory.
Creating or altering tables to use DSE In-Memory
Use CQL directives to create and alter tables to use DSE In-Memory.
Verifying table properties
In cqlsh, use the DESCRIBE command to view table properties.
Managing memory
You must monitor and carefully manage available memory when using DSE In-Memory.
Backing up and restoring data
The procedures for backing up and restoring data is the same procedure for DSE In-Memory data and on-disk data.
Deploying
Production deployment of DataStax Enterprise includes planning, configuration, and choosing how the data is divided across the nodes in the cluster.
Production deployment planning
Resources for deployment planning and recommendations for deployment.
Configuring replication
How to set up DataStax Enterprise to store multiple copies of data on multiple nodes for reliability and fault tolerance.
Mixing workloads
Organize nodes that run different workloads into virtual data centers. Put analytic nodes in one data center, search nodes in another, and Cassandra real-time transactional nodes in another data center.
Single data center deployment per workload type
Steps for configuring nodes in a deployment scenario in a mixed workload cluster that has only one data center for each type of workload.
Multiple data center deployment per workload type
Steps for configuring nodes in a deployment scenario in a mixed workload cluster that has more than one data center for each type of node.
Single-token architecture deployment
Steps for deploying when you are not using virtual nodes (vnodes).
Calculating tokens for single-token architecture nodes
When not using vnodes, use these steps to calculate tokens to evenly distribute data across a cluster.
Expanding an AMI cluster
To expand your EC2 implementations, use OpsCenter.
DataStax Enterprise data migration
Migrate data using Sqoop or other methods.
Migrating data using Sqoop
For DSE Hadoop, use Sqoop to transfer data between an RDBMS data source and Hadoop or between other data sources, such as NoSQL.
Migrating data
Migrating data to DataStax Enterprise solutions include the COPY command, the DSE Search/Solr Data Import Handler, and the Cassandra bulk loader.
Bulk saving data from Spark RDD to Cassandra
Bulk saving data from Spark RDD to Cassandra bypasses the standard Cassandra write-path.
Tools
Tools include dse commands, dsetool, dfs-stress tool, pre-flight check and yaml_diff tools, and the Cassandra bulk loader.
dse commands
The dse commands provide additional controls for starting and using DataStax Enterprise.
dsetool utility
Use the dsetool utility for creating system keys, encrypting sensitive configuration information, and performing Cassandra File System (CFS) and Hadoop-related tasks, such as checking the CFS, and listing node subranges of data in a keyspace.
The cfs-stress tool
The cfs-stress tool performs stress testing of the Cassandra File System (CFS) layer.
Pre-flight check and yaml_diff tools
The pre-flight check tool is available for packaged installations. This collection of tests can be run on a node to detect and fix a configuration. The yaml_diff tool filters differences between cassandra.yaml files.
Using the Cassandra bulk loader in a secure environment
The Cassandra bulk loader is the sstableloader tool.
Troubleshooting
Use these troubleshooting examples to discover and resolve problems with DSE.
Release notes
DataStax Enterprise release notes cover cluster requirements, upgrade guidance, components, changes and enhancements, issues, and resolved issues for DataStax Enterprise 4.7 releases.
Cassandra changes
DataStax Enterprise 4.7 includes production-certified Cassandra changes.