DataStax Enterprise (DSE) Service is an automated service that makes it easy to deploy and manage DataStax Enterprise clusters on Mesosphere DC/OS, eliminating nearly all of the complexity traditionally associated with managing a DataStax cluster. DataStax Enterprise helps customers of all sizes build and run cloud-native applications at epic scale. Our customers have been using our technology to build personalization, IoT, Customer 360 type applications, just to name a few. Inside DataStax Enterprise, you will find Solr to power our Search capability, Spark for Analytics, and a graph database for highly connected data sets. Multiple DataStax clusters can be installed on DC/OS and managed independently, so you can offer DataStax Enterprise as a managed service to your organization.
- Auto-configured OpsCenter (datastax-ops package) or point to external OpsCenter.
- Multiple instances sharing the same physical systems (requires custom port configuration).
- Vertical (resource) and horizontal (node count) scaling.
- Easy redeployment to new systems upon scheduled or unscheduled outages.
- Consistent DNS addresses regardless of where nodes are located in the cluster.
- Node placement may be customized via Placement Constraints.
Installing and Customizing
The service comes with reasonable defaults for trying it out, but which should not be used in production. See note below.…Read More
Deployment Best Practices
NOTE: Repeat the steps below if you need to uninstall DataStax Enterprise OpsCenter, but replace datastax-dse with datastax-ops.…Read More
In this example, you can access the Opscenter UI directly via the native endpoints in your local browser at 10.0.3.156:8888 or opscenter-0-node.datastax-ops.autoip.dcos.thisdcos.directory:8888.…Read More
DSE in DC/OS currently supports both internal and ldap authentication/authorization schemes. You can configure both schemes and then select the order in which they are used, or you can configure just one, in which case only that scheme will be used. DSE will try to authenticate with the default scheme first and fall back to the alternate scheme if it has been configured. More information about how DSE handles this can be found in DataStax’s documentation…Read More
You can make changes to the service after it has been launched. Configuration management is handled by the scheduler process, which in turn handles deploying DSE itself.…Read More
The DC/OS DataStax Enterprise (DSE) Service implements a REST API that may be accessed from outside the cluster. The
DC/OS does not provide any specific disaster recovery capabilities. As such, a disaster recovery plan must center around features of DSE. Regular backups should be performed via the DSE OpsCenter Backup Service in production environments. Backups and restores should be tested in a staging environment.…Read More
Logs for the Scheduler, DSE Nodes, and OpsCenter instance (if used), may all be browsed via the DC/OS Dashboard.…Read More
A manual nodetool removenode call is currently required when replacing nodes. This is planned to be automated in a future release.…Read More
Packages are versioned with an a.b.c-x.y.z format, where a.b.c is the version of the service management layer and x.y.z indicates the version of DSE. For example, 1.5.0-3.2.1 indicates version 1.5.0 of the service management layer and version 3.2.1 of DSE.…Read More
Create an options.json file with your existing installation options. If you saved a copy during initial install, you can use that. If you don’t have it, follow the steps in the “Recreating options.json” section of the management docs. When you have obtained your options.json file, place a copy of it in $HOME/options.json.…Read More
We support upgrade/rollback between adjacent versions only. Concretely, to upgrade from version 2 to version 4, you must upgrade from 2 -> 3, then from 3 -> 4.…Read More