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

Every read triggers a read-repair when Last-write-wins=true #334

Merged
merged 1 commit into from
Jan 31, 2013
Merged

Every read triggers a read-repair when Last-write-wins=true #334

merged 1 commit into from
Jan 31, 2013

Commits on Jan 31, 2013

  1. Fix write on read bug with lww+bitcask 

    Fixes issue #334.
Reading a value written into a bucket with last write wins set to true
when using a non index supporting backend (bitcask) was causing
read-repairs writes.  The problem is the logic was causing all replica
writing nodes to increment the vclock, instead of just incrementing in
the coordinating node and forwarding to replicas as normally happens.
    @engelsanchez
    engelsanchez committed Jan 31, 2013
    1 Configuration menu
    Copy the full SHA
    8895d28 View commit details
    Browse the repository at this point in the history