Hi, I hope this script will help someone. (attached)
It reads all buckets and for each bucket it gets the keys and read all the
entries.
Could be potentially useful after the restart of a node.
-tony
On Thu, Sep 1, 2011 at 9:22 AM, Sean Cribbs <s...@basho.com> wrote:
> You will need to do so manually. Riak currently has no active anti-entropy
> (expect the EDS product which has a kind of it in the long-haul
> replication).
>
>
> On Thu, Sep 1, 2011 at 9:20 AM, Tony Bussieres <t.bussie...@gmail.com>wrote:
>
>> Hi Andrew,
>>
>> Can we automatically, after restarting a node, read-repair all entries
>> using the command line?
>> Or we have to read all keys individually so they become consistent?
>>
>> -tony
>>
>>
>> On Wed, Aug 31, 2011 at 5:27 PM, Andrew Thompson <and...@hijacked.us>wrote:
>>
>>> On Wed, Aug 31, 2011 at 05:11:16PM -0400, Tony Bussieres wrote:
>>> > Hi,
>>> >
>>> > We have a cluster of two nodes.
>>> >
>>> > We add keys to a bucket :
>>> > curl -v -X PUT -d '{"prop":"val"}' -H "Content-Type: application/json"
>>> > http://riak/store/jdTestBucket/key1?w=1
>>> > curl -v -X PUT -d '{"prop":"val"}' -H "Content-Type: application/json"
>>> > http://riak/store/jdTestBucket/key2?w=1
>>> > curl -v -X PUT -d '{"prop":"val"}' -H "Content-Type: application/json"
>>> > http://riak/store/jdTestBucket/key3?w=1
>>> > curl -v -X PUT -d '{"prop":"val"}' -H "Content-Type: application/json"
>>> > http://riak/store/jdTestBucket/key4?w=1
>>> >
>>> > We shut down one node.
>>> >
>>> > We delete the keys:
>>> > curl -v -X DELETE http://riak/store/jdTestBucket/key1?w=1
>>> > curl -v -X DELETE http://riak/store/jdTestBucket/key2?w=1
>>> > curl -v -X DELETE http://riak/store/jdTestBucket/key3?w=1
>>> > curl -v -X DELETE http://riak/store/jdTestBucket/key4?w=1
>>> >
>>> >
>>> > We list the keys :
>>> > curl -i http://riak/store/jdTestBucket?keys=true\&props=false
>>> >
>>> > All keys are listed.
>>> >
>>> > Is it normal?
>>> >
>>>
>>> Yes, keys are only deleted when all the values are tombstones and all
>>> the nodes are up. In theory bringing the other node back up and
>>> re-reading the keys will read-repair the keys on the node that was down
>>> to be tombstones and then hopefully they'll be removed.
>>>
>>> However, deletes are flaky on 0.14. Things should be a little better in
>>> 1.0.
>>>
>>> Andrew
>>>
>>> _______________________________________________
>>> riak-users mailing list
>>> riak-users@lists.basho.com
>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.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/
>
>
read_repair.sh
Description: Bourne shell script
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
