Skip to content
This repository

Incorrectly detected write lock #43

jonmeredith opened this Issue April 10, 2012 · 2 comments

3 participants

Jon Meredith Scott Lystig Fritchie Dmitry Groshev
Jon Meredith

After crash, bitcask does not always detect stale locks correctly. Here is an example from a crashed Riak node.

07:25:13.738 [error] Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.25793.657> exit with reason bad return value: {error,{write_locked,locked,"/var/lib/riak/bitcask/536645132457440915277915524513010171279912730624"}} in context child_terminated
Dmitry Groshev
si14 commented April 10, 2012

+1 here. I'm using bitcask separately from Riak and I've got the same problem.

Scott Lystig Fritchie

Hiya. I believe that this problem has been fixed by #68. I have one more small lockfile-related fix to make, hopefully later today. If there's still a problem, please reopen.

Scott Lystig Fritchie slfritchie closed this November 16, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.