This documentation describes the a9s Elasticsearch service. a9s Elasticsearch enables on-demand provisioning of VM-based, dedicated Elasticsearch servers and clusters. Developers can create instances of a Elasticsearch server or cluster using the Cloud Foundry Command Line interface (cf CLI) and bind these instances to an application. Depending on your service plan, a service instance may be associated with a single, dedicated VM or a set of VMs consisting of multiple VMs containing an Elasticsearch replica set cluster.
When you run the cf CLI
create-service elasticsearch command, BOSH creates dedicated VMs for this service instance. This allows the best possible bad neighborhood protection.
Elasticsearch service instance provisioning, including VM orchestration, is entirely automated. This enables service instances to be highly isolated and shielded by infrastructure virtualization mechanisms.
Distributed across multiple infrastructure availability zones, clustered data service plans enable short failover times and are resilient against failures of individual infrastructure hosts or entire availability zones.
The current version of a9s Elasticsearch includes the following key features:
|On-Demand Service Instance Provisioning||a9s Elasticsearch fdeploys Elasticsearch instances automatically. Developers can provision a single-VM Elasticsearch server or a multi-VM Elasticsearch Replica Set using a single command.|
|Service Instance Isolation||Each Elasticsearch server runs on a dedicated VM to ensure bad neighborhood protection in order to be aligned with enterprise security requirements. |
a9s Elasticsearch uses Cloud Foundry security groups to prevent network connections being established by unauthorized applications.
|High Availability||a9s Elasticsearch ensures high-availability. |
The Consul-based internal DNS system ensures that the connected application always connects to a working node.
|Smoke Tests||a9s Elasticsearch contains a post-deploy smoke tests errand that runs a series of basic test against your installation to ensure that it is configured properly.|
|Service Instance Capacity Upgrade||Cloud Foundry Service Plan updates allow upgrades to the RAM, CPU and storage capacity for your Elasticsearch instances.|
|Logging and Monitoring||Each Elasticsearch service instance provides log messages and Elasticsearch-specific metrics to one or more |
|Deployment Updater||This errand automatically updates the stemcell and all provisioned a9s Elasticsearch service instances to their lastest version.|
|Backup Manager||The Backup Manager does regular backup of your instances and offers endpoints to backup instantly and restore backups.|
|Service Guard||The Service Guard creates Cloud Foundry security groups for your service instance VMs. |
When the IP address of a service instance changes, the guard updates the security group. The Service Guard also restarts the application instances bound to the affected service instance. The instances of one application are restarted one by one to avoid downtime.
Specification of a9s Elasticsearch service plans:
|High Availability |
(number of nodes)
|Number of vCPUs||2||2||2||2||2||2|
|RAM||2 GB||2 GB||4 GB||2 GB||4 GB||4 GB|
|Disk *||4 GB||10 GB||50 GB||10 GB||50 GB||150 GB|
For example, one backing service instance of size m is high available (consists of 3 nodes), has 2 vCPUs, 4 GB RAM, 50 GB disk and logging component.
* Total virtual disk size. You cannot use the whole disk for your data. For more information, refer Disk Alerts.
Any questions left?
Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.