Re: Deleted keys come back

2015-10-09 Thread mtakahashi-ivi
Hello, Thank you all and sorry for replying so late. W=2 works. "allow_mult" is not suitable for me. Because sibling affects results of Yokozuna search. > Also, to make sure your data eventually consistent, R+W > should be > N. Your case is 1+1, not >2. Right. I'm not indended but, I can't ch

bitcask dead byte and fragment for riak-cs

2015-10-09 Thread Mohamad Taufiq
Hello there, i have problems with my riak-cs cluster. i have 5 riak nodes, each node have 11 TB of storage. my riak-cs deployment is just following 5 minutes installation tutorial. but, after running for 1 month. surprisingly, i have storage problem. my bitcask folder (/data/riak/bitcask) is sto

Re: Node join not committed

2015-10-09 Thread Daniel Iwan
Hi Jon Thanks for confirming this. We did do plan/commit and everything worked as expected, no issues whatsoever Thanks a bunch Daniel -- View this message in context: http://riak-users.197444.n3.nabble.com/Node-join-not-committed-tp4033571p4033573.html Sent from the Riak Users mailing list a

Re: Node join not committed

2015-10-09 Thread Jon Meredith
Hi Daniel, It's perfectly safe to issue the cluster plan/commit steps. Joining the node gives it information about where data is located in the rest of the cluster and it will happily coordinate gets, but the new node will always forward put requests and will not store any data until you go throu

Node join not committed

2015-10-09 Thread Daniel Iwan
Hi Our attach script failed and it only issued *cluster join* but not *cluster plan* and *cluster commit*. so the node was visible as joining in member_status Since then both part (original cluster and new node) were taking writes but in our configuration each node takes writes from it local proc