Re: Keys aren't deleted

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 wrote: > You will need to do so manually. Riak

Re: Keys aren't deleted

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 wrote: > Hi Andrew, > > Can we automatically, after restarting a node, read-repair all entries >

Re: Keys aren't deleted

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 wrote: > On Wed, Aug 31, 2011 at 05:11:16PM -0400, Tony Bussiere

Re: Keys aren't deleted

On Wed, Aug 31, 2011 at 05:35:09PM -0400, Jonathan Langevin wrote: > What if a node were permanently removed for some odd reason? You could never > delete those keys in that situation?* > Then you should remove that node from the cluster and do a read-repair. That should make the tombstones go aw

Re: Keys aren't deleted

What if a node were permanently removed for some odd reason? You could never delete those keys in that situation?* Jonathan Langevin Systems Administrator Loom Inc. Wilmington, NC: (910) 241-0433 - jlange...@loomlearning.com - www.loomlearning.com - Skype: intel352

Re: Keys aren't deleted

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 "Conte