Raft uses BoltDB #857
Merged
Raft uses BoltDB #857
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is awesome! |
|
I'm editing the internals/consensus.html doc now. I should update all references to LMDB to BoltDB, right? |
|
@ryanbreen not all of them, actually. We still use an in-memory only LMDB for Consul's state store, so for example, the FAQ entry about virtual memory size should be left intact until we completely remove it in 0.6. Anything specifically about the Raft log + LMDB can be updated though. |
|
Thanks! Is this line still true wrt Bolt?
|
|
BoltDB supports MVCC so this should still hold true with that backend. So yep! |
ryanbreen
added a commit
that referenced
this pull request
Apr 11, 2015
…g LMDB references in favor of BoltDB per GH-857.
artushin
added a commit
to artushin/consul
that referenced
this pull request
Apr 22, 2015
* upstream/master: (191 commits) Fix invalid link to sessions page Upstart: Consul leave now works as expected. Caps not necessary here Updating the docs to include information about registering a check with a serviceid. ampersand add consul and the hc ecosystem Website: minor fix for docs/agent/http/agent.html. Website: cleanup for docs/internals/sessions.html. agent: parse raw query URL to avoid closing the request body early Website: cleanup for docs/internals/security.html. Website: minor tweaks for docs/internals/jepsen.html. agent: hide tokens from logs and monitor Add XXX to the end of mktemp template to support more linux versions. Website: fix caps issue in docs/internals/consensus.html. Build consul to a temp dir for API tests Website: revert link to securing Consul doc since it's not ready yet. Website: minor additional tweaks for docs/internals/consensus.html. Website: cleanup for docs/internals/consensus.html, including removing LMDB references in favor of BoltDB per hashicorpGH-857. agent: Don't attempt migration on new server Update CHANGELOG.md ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switches over to the raft-boltdb backend for persisting the Raft log. There are a few things to note about these changes: