Beta Elastic 2.1.2-5.6.5-beta

DC/OS Elastic Service is an automated service that makes it easy to deploy and manage Elastic on Mesosphere DC/OS, eliminating nearly all of the complexity traditionally associated with managing an Elasticsearch cluster. Elasticsearch is a distributed, multitenant-capable, full-text search engine with an HTTP web interface and schema-free JSON documents. Elasticsearch clusters are highly available, fault tolerant, and durable. For more information on Elasticsearch, visit the Elastic site. Multiple Elasticsearch clusters can be installed on DC/OS and managed independently, so you can offer Elasticsearch as a managed service to your organization with or without the commercial X-Pack capabilities.


DC/OS Elastic offers the following benefits of a semi-managed service:

  • Easy installation
  • Elastic scaling of nodes
  • Replication for high availability
  • Elasticsearch cluster and node monitoring


DC/OS Elastic provides the following features:

  • Single-command installation for rapid provisioning
  • Multiple clusters for multiple tenancy with DC/OS
  • High availability runtime configuration and software updates
  • Storage volumes for enhanced data durability, known as Mesos Dynamic Reservations and Persistent Volumes
  • Automatic reporting of Elasticsearch metrics to DC/OS statsd collector

Install and Customize

To start a basic cluster with three master nodes, two data nodes, and one coordinator node, run the following command on the DC/OS CLI:…Read More


X-Pack is an Elastic Stack extension that bundles security, alerting, monitoring, reporting, and graph capabilities into one easy-to-install package. X-Pack is a commercial product of Elastic that requires a license. By default, X-Pack is not installed as part of the DC/OS Elastic service. However, it’s easy to enable X-Pack as part of the service configuration:…Read More

Custom Elasticsearch YAML

Many Elasticsearch options are exposed via the package configuration in config.json, but there may be times when you need to add something custom to the elasticsearch.yml file. For instance, if you have written a custom plugin that requires special configuration, you must specify this block of YAML for the Elastic service to use.…Read More


If you are using DC/OS 1.10 and the installed service has a version greater than 2.0.0-x:…Read More

Quick Start

Perform a default installation by following the instructions in the Install and Customize section of this topic. Note: Your DC/OS cluster must have at least 3 private agent nodes.…Read More

Connecting Clients

The Elasticsearch REST APIs are exposed using JSON over HTTP. You simply send HTTP requests to the appropriate Named VIP, which is essentially a load-balanced name-based service address. By default, the Elastic framework creates an Elasticsearch cluster with one coordinator node. Send your requests to this service address as shown in the following examples:…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 DC/OS Elastic Service itself.…Read More

API Reference

The DC/OS Elastic Service implements a REST API that may be accessed from outside the cluster. The parameter referenced below indicates the base URL of the DC/OS cluster on which the Elastic Service is deployed.…Read More

Disaster Recovery

You interact with the Elasticsearch cluster directly to perform snapshot and restore operations. Elasticsearch’s built in snapshot and restore module allows you to create snapshots of individual indices or an entire cluster into a remote repository like a shared file system, S3, or HDFS.…Read More


The DC/OS Elastic Service is resilient to temporary node failures. However, if a DC/OS agent hosting an Elastic node is permanently lost, manual intervention is required to replace the failed node. The following command should be used to replace the node residing on the failed server.…Read More


The maximum number of deployable nodes is constrained by the DC/OS cluster’s resources. Each Elasticsearch node has specified required resources, so nodes may not be placed if the DC/OS cluster lacks the requisite resources.…Read More

Supported Versions

…Read More

Release Notes

This is a beta release of the DC/OS Elastic service. It contains multiple improvements as well as new features that are to be considered of beta quality. Do not operate this version in production.…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