EDIT: I think we're talking about two different options. I meant the ability to leave sync turned on but change the data structure.
EDIT: I think we're talking about two different options. I meant the ability to leave sync turned on but change the data structure.
Just to be clear, we are talking about this item from the post-mortem right?
> We are working closely with HashiCorp to deploy a new version of Consul that replaces BoltDB with a successor called bbolt that does not have the same issue with unbounded freelist growth.
EDIT: I see what you mean. The freelist improvement has to be enabled by setting the `FreelistType` config to "hashmap" (default is "array"). Indeed it doesn't look like consul has done that...
I mean the optional called `FreelistType` has a new option called `FreelistMapType` and the default is `FreelistArrayType`. There is no option in Consul from what I can tell to configure that option. They did have to upgrade from the old boltdb code to the etcd boltdb code to do this though.