Re: Upgrading consul-release to consul 0.6.0

Amit Kumar Gupta

Hi Gwenn

Thanks for your feedback, and taking the time to look through the changelog!

cf-release/consul-release have been on 0.5.2 (post BoltDB migration) since
Jun 2015:
So there should be no concerns around any migrations from LMDB.


On Wed, Feb 3, 2016 at 6:04 PM, Gwenn Etourneau <getourneau(a)>

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. "*
* Consul should be provisioned with physical memory approximately 2X the
data set size to allow for bursty allocations and subsequent garbage

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

Hi cf-dev, cf-diego

The CF Infrastructure team which maintains 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:
* 0.6.1:
* 0.6.2:

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.

Amit, CF Infrastructure team PM

Join to automatically receive all group messages.