I think the problem you are having here is that you are using an invalid
bucket name.
"buyseasons/products" would actually refer to a bucket/key pair. Riak
doesn't have nested buckets.
If you change your bucket name to "buyseasons-products" or
"buyseasons%20products" it should work.
As for the
Hey Kevin,
It looks like only RiakClient.ListKeys(), RiakClient.ListKeysStream(), and
RiakClient.DeleteBucket() will give you that warning.
You shouldn't see it popup from anywhere else in CorrugatedIron.
Thanks,
Alex
On Sat, Feb 9, 2013 at 11:19 PM, Kevin Burton wrote:
> One more question I h
Hey Elias,
It's referring to the vnode replicas on the node you are replacing. Doing
a force-replace reassigns all that nodes partitions without handing them
off, so the replicas on that node are "lost". However, since riak
replicates to 'N' physical nodes, there should be other replicas of your
In that case you wouldn't actually lose any data, since the data
directories would be there the whole time.
The force-replace command will always give that warning though.
Thanks,
Alex
On Fri, Apr 5, 2013 at 5:07 PM, Elias Levy wrote:
> On Fri, Apr 5, 2013 at 1:51 PM, Alexander Moo
Hi Yuri,
What backend are you using?
What does riak-admin ring-status output?
Thanks,
Alex
On Fri, Apr 5, 2013 at 6:30 PM, Yuri Lukyanov wrote:
> Hi,
>
> I was adding the 7-th node to one of our riak 1.2 clusters. Everything was
> ok untill the process suddenly stopped with one handoff lef
Also, what's the output of riak-admin ringready ?
Thanks,
Alex
--Alex
On Fri, Apr 5, 2013 at 6:37 PM, Alexander Moore wrote:
> Hi Yuri,
>
> What backend are you using?
>
> What does riak-admin ring-status output?
>
> Thanks,
> Alex
>
>
>
>
> O
Hi Bhuwan,
That error usually means that you are overloading your cluster in some
fashion.
To fix this you could try a rolling restart of your nodes.
To find the root cause though, can you reply with the following information:
What are the ulimit settings on your riak machines?
Are you running a
Hi Sanjeev,
By default, uploaded objects will not be publicly available. To make them
available you have to set the Access Control List to allow public reads for
all users.
If you are using s3cmd you can do this with: *s3cmd -c .s3cfgfile setacl
--acl-public s3://BUCKET/OBJECT*
If you need to do