Hmm...ok. Will have to ponder how we can fix that. Thanks!
D. On Mon, May 9, 2011 at 8:09 AM, Nico Meyer <nico.me...@adition.com> wrote: > Hi Dave, > > I believe problem occours if there happens to be another process with > the same PID as the old (now gone) riak node. This can happen if the > machine was rebooted since the riak node crashed or if the PIDs wrapped, > they are only two bytes after all. > os_pid_exists/1 only checks for ANY process with the PID from the > lockfile > (https://github.com/basho/bitcask/blob/master/src/bitcask_lockops.erl#L116). > > > > Am Montag, den 09.05.2011, 07:06 -0600 schrieb David Smith: >> On Sat, May 7, 2011 at 9:25 AM, Gary William Flake <g...@flake.org> wrote: >> > That was it, Nico. Thanks. >> > >> > I know we did a forced shutdown this week, which was probably the cause. >> > But I would have thought that riak would have taken care of its own lock >> > file bookkeeping on restarting. >> >> Bitcask does: >> >> https://github.com/basho/bitcask/blob/master/src/bitcask_lockops.erl#L46 >> >> It's curious that the logic didn't handle the case. What platform/OS >> are you on? Are you using init scripts to restart on boot? >> >> Thanks, >> >> D. > > > -- Dave Smith Director, Engineering Basho Technologies, Inc. diz...@basho.com _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
