1. Cf-Dev
  2. Messages

Re: Upgrading consul-release to consul 0.6.0

Gwenn Etourneau
 

My biggest concern is the Data migration from LMDB to BoltDB, I know there
is a CLI to do that but I am concern about the migration of the DATA itself.


*" Previously, Consul would automatically detect data directories using the
old LMDB format, and convert them to the newer BoltDB format. This
automatic upgrade has been removed for Consul 0.6, and instead a safeguard
has been put in place which will prevent Consul from booting if the old
directory format is detected. "*
*AND*
* Consul should be provisioned with physical memory approximately 2X the
data set size to allow for bursty allocations and subsequent garbage
collection.*

On Thu, Feb 4, 2016 at 3:28 AM, Amit Gupta <agupta(a)pivotal.io> wrote:

Hi cf-dev, cf-diego

The CF Infrastructure team which maintains consul-release (
https://github.com/cloudfoundry-incubator/consul-release) is considering
bumping from consul 0.5.2 to 0.6.0. There are many changes between those
consecutive releases, which you can read about here:

* 0.6.0:
https://github.com/hashicorp/consul/blob/master/CHANGELOG.md#060-december-3-2015
* 0.6.1:
https://github.com/hashicorp/consul/blob/master/CHANGELOG.md#061-january-6-2016
* 0.6.2:
https://github.com/hashicorp/consul/blob/master/CHANGELOG.md#062-january-13-2016

We would like to explore this bump to get the change in 0.6.0 where consul
moved to a pure Go implementation, allowing us to avoid having to set
GOMAXPROCS when starting the consul server, and then some of the security
fixes in 0.6.2 for good measure.

This change would also affect clients of the consul server in
consul-release, hopefully in mainly positive ways. If you're a consumer of
consul-release as a client, I would appreciate your feedback on this
potential bump to consul in consul-release.

Thanks,
Amit, CF Infrastructure team PM

attachment.html

attachment.html

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.