On 11/26/12 1:09 PM, "Matthew Von-Maszewski" <matth...@basho.com> wrote:
>Alex,
>
>The eleveldb backend creates a CRC for every item placed on the disk.
>You can activate the test of the CRC on every read by adding:
>
> {verify_checksums, true},
>
>to the "{eleveldb " portion of app.config. With riak 1.2, you must
>manually monitor each vnode directory for the lost/BLOCKS.bad file
>changing size. It only increases upon read operations detecting a CRC
>and/or compression corruption error.
>
>Manually monitoring the BLOCKS.bad file is tacky (my apologies). The
>upcoming 1.3 release will populate riak admin with a counter of errors
>seen. But that code is still weeks from release.
Thank you for working on this feature!
This is great to hear. A few questions about the new 1.3 functionality:
- What will happen to the read when this occurs?
- Will this trigger a read repair when it happens?
--
paul
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
