1.8 KiB
title | description | menu | ||||||
---|---|---|---|---|---|---|---|---|
Migrate to a Chronograf HA configuration | Migrate a Chronograf single instance configuration using BoltDB to a Chronograf high-availability (HA) cluster configuration using etcd. |
|
Use chronoctl
to migrate your Chronograf configuration store from BoltDB to a shared etcd
data store used for Chronograf high-availability (HA) clusters.
Note: Migrating Chronograf to a shared data source creates new source IDs for each resource. Update external links to Chronograf dashboards to reflect new source IDs.
-
Stop the Chronograf server by killing the
chronograf
process. -
To prevent data loss, we strongly recommend that you back up your Chronograf data store before migrating to a Chronograf cluster.
-
Run the following command, specifying the local BoltDB file and the
etcd
endpoint beginning withetcd://
. (We recommend adding the prefixbolt://
to an absolute path. To specify a relative path to the BoltDB file, the prefix cannot be used.)$ chronoctl migrate -f bolt:///path/to/chronograf-v1.db -t etcd://localhost:2379
Note: If you have authentication on
etcd
, use the standard URI format to define a username and password. For example,etcd://user:pass@localhost:2379
-
Update links to Chronograf (for example, from external sources) to reflect your new URLs:
-
Set up a load balancer for Chronograf.