2.0.3

Upgrade to explorer to 1.4.1 version

2.0.2

Update explorer version

2.0.1

Update explorer version

2.0.0

Adds multiple Riak versions support. Each cluster may be created with its own Riak (KV or TS).
Adds ability to import/export structure of clusters.
Extends cluster info endpoint responses to include node info.
Resources management improvements.

1.8.2

Changes:

• #94 Adds ability to start scheduler with dist-erl on, allowing remote attach for live debug/trace functionality

1.8.1

Changes:

• #93 Bump riak_explorer to v1.2.1

1.8.0

Changes:

• #90 Upgrade riak_explorer to 1.2.0
• #91 Inspect the riak archive for the path under which it will extract, and pass that to the executor.

1.7.1

Changes:

• #89 new default values for .riak.hostname and .riak.role derived from .riak.framework-name if unset in config.json

1.7.0

Changes:

• #84 #87 : Rework how config files for Riak are managed: no longer do we automatically set a default config file, and we allow the config files to be deleted once set.

Note that for this to be compatible with Executor versions before 1.5.0, you MUST set a config and advanced-config file for your clusters.

1.6.0

IMPORTANT: if you upgrade to this release and use a custom configuration, you must change your riak.conf so that it sets platform_data_dir = ../../data. If you use the default config that ships with the scheduler, this has been updated already.

Changes:

• #85 Move persistent volume path; ensure no archive contents clobber PV path

If you are running a Riak cluster on Mesos with a previous version of this scheduler and want to update, do not simply update the config.json, reinstall the scheduler and perform a riak-mesos cluster restart: this will lead to data loss.

Instead, you will need to update the config.json and reinstall the scheduler, then slowly migrate your cluster to new nodes, allowing transfers to finish before removing each old node.

For a much more in-depth write-up of the procedure, see here: https://gist.github.com/sanmiguel/aa06f1e6026601677af2ced87c6a35f9#file-live-upgrade-procedure-sh

If in doubt, please contact us via the issues.