This bug was recently fixed -- although the option was available to bitcask
it was not applied when started by the KV backend. (
https://github.com/basho/riak_kv/commit/51290526d1e3c0408e6238a55b676809e1b0c840)
However, it may be possible that somewhere inside Bitcask, the osync
strategy is not enacted, but I'll leave that determination to Dizzy.
On Wed, Aug 31, 2011 at 12:22 AM, David Smith <diz...@basho.com> wrote:
> On Tue, Aug 30, 2011 at 8:57 PM, Tatsuya Kawano <tatsuya6...@gmail.com>
> wrote:
>
> > The current behavior could be dangerous if someone rely on
> {sync_strategy, o_sync} for durability.
> >
> > My colleague checked Bitcask implementation and found that it uses "fcntl
> (2)" system call to set O_SYNC flag to the file descriptor. Unfortunately,
> O_SYNC being set by this way will be ignored by kernel and has no effect. To
> make it work, Betcask should call "open" system call with O_SYNC option.
>
> Tatsuya, thanks for the pointer on this. I will take a look into this
> more carefully tomorrow.
>
> 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
>
--
Sean Cribbs <s...@basho.com>
Developer Advocate
Basho Technologies, Inc.
http://www.basho.com/
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
