Skip to content
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.

Sign up for GitHub

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

Jump to bottom

During burst writes WAL files could cause a too many open files error #516

Closed
jvshahid opened this issue May 7, 2014 · 0 comments
Closed

During burst writes WAL files could cause a too many open files error #516

jvshahid opened this issue May 7, 2014 · 0 comments
Milestone
0.6.3

Comments

@jvshahid
Copy link
Contributor

jvshahid commented May 7, 2014

If we received a burst of writes that leveldb can't keep up with, the wal files are kept open until they are deleted which will cause the process to run out of file descriptors. We should close the files as soon as we're done with them, only open them when we're appending or replaying from them. This is the cause of #515
@jvshahid jvshahid added this to the 0.6.2 milestone May 7, 2014
@jvshahid jvshahid self-assigned this May 7, 2014
@jvshahid jvshahid mentioned this issue May 7, 2014
Closed
@jvshahid jvshahid modified the milestones: Next release, 0.6.2, 0.6.3 May 12, 2014
jvshahid added a commit that referenced this issue May 27, 2014
@jvshahid @pauldix
Fix #516. Close WAL log/index files if they aren't needed anymore
0a7da3f
@jvshahid jvshahid removed their assignment Feb 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.6.3
Development

No branches or pull requests
1 participant
@jvshahid