-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move WAL out of BoltDB #3514
Milestone
Comments
This would be wonderful. |
Seems that the same issue is very important in my case, hope fix will be provided soon. |
Waiting for this one also ;-) |
While you guys are waiting for this, I am urgently waiting for it :) |
Closed
+1 |
2 similar comments
+1 |
+1 |
Done in #3569 and on 0.9.3-rc1, which I'm cutting right now. Testing and performance results are greatly appreciated! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having the WAL in BoltDB is causing the entire database to lock during WAL flushes, which is causing write timeouts. Move the WAL outside of Bolt and ensure that flushes of the WAL do not cause the database to lock for writes.
WAL should be able to flush incrementally. It should gradually put on back pressure if the index is unable to keep up with the pace of WAL flushing. Ideally this should occur over time rather than as a large timeout.
The text was updated successfully, but these errors were encountered: