ArangoDB is a distributed, multi-model database featuring JSON documents, graphs, and key/value pairs. It has a unified query language (AQL) that allows you to mix all three data models and supports joins and transactions.
Anyone who wants to deploy a distributed multi-model database on DC/OS. Beginner level.
This tutorial covers the basics to get you started with ArangoDB on DC/OS.
- A running DC/OS cluster
- DC/OS CLI installed
Install ArangoDB on DC/OS
The DC/OS CLI provides a convenient way to deploy applications on your DC/OS cluster.
Deploying ArangoDB via the DC/OS CLI is as easy as:
dcos package install arangodb3
This command installs the
arangodb3 subcommand and starts an instance of the ArangoDB service with its default configuration under its standard name, “arangodb3” via Marathon.
Open the DC/OS web interface in your browser and click the Services tab to watch ArangoDB start up on your Open DC/OS cluster:
Click the ArangoDB task to reveal the subtask that the framework has started:
Click “Open Service” to open the ArangoDB web interface.
Congratulations! You now have ArangoDB running on DC/OS.
Using ArangoDB within the DC/OS cluster
Now that ArangoDB is running you can fill it with some data and use it as a data store for your applications.
To get started, talk to the “Coordinators” of your ArangoDB cluster. You should not hardcode the “Coordinators” IP addresses and ports in your applications because they can move or change at any time throughout your cluster lifetime (e.g. tasks might fail, up- and downscaling) .
To connect to ArangoDB from the inside deploy the ArangoDB Mesos HAProxy.
Clone the repository and start the proxy:
git clone https://github.com/arangodb/arangodb-mesos-haproxy cd arangodb-mesos-haproxy dcos marathon app add marathon.json
To make your proxy highly available or scale it, you can simply add a few more instances via the Marathon UI.
Use the following commands to shut down and delete your ArangoDB service and the command line tool:
dcos arangodb3 uninstall; dcos package uninstall arangodb3
The first command uses the
arangodb subcommand to gracefully shut down and
delete all instances of your ArangoDB service. The framework scheduler
itself will run in silent mode for another 120 seconds. This enables
the second command to remove the
arangodb subcommand and the entry in
Marathon that would otherwise restart the framework scheduler
There are a number of configuration options, which can be specified in the following way:
dcos package install --config=<JSON_FILE> arangodb
JSON_FILE is the path to a JSON file. For a list of possible
attribute values and their documentation see
dcos package describe --config arangodb
For further information, visit: https://github.com/arangoDB/arangodb-mesos-framework
The ArangoDB service is also distributed in binary form as a Docker image: arangodb/arangodb-mesos-framework
See the README.md in the framework repository for details on how the framework scheduler is configured.
Support and bug reports
The ArangoDB Mesos framework and the DC/OS subcommand are supported by ArangoDB GmbH, the company behind ArangoDB. If you get stuck, need help or have questions, just ask via one of the following channels:
- Google Group
firstname.lastname@example.org: developer mailing list of ArangoDB
email@example.com: direct email to Max Neunhöffer
firstname.lastname@example.org: direct email to Frank Celler
email@example.com: direct email to Andreas Streichardt
Additionally, we track issues, bug reports, and questions via the GitHub issue trackers at