Hi Shunichi,
Enabling that temporarily then enabled me to remove the buckets by
first creating (s3cmd mb) and then removing (s3cmd rb) the problematic
buckets.
Thanks,
Toby
On 7 July 2014 19:38, Shunichi Shinohara wrote:
> Hi Toby,
>
> There is a rarely used option "disable_local_bucket_check" i
Hi Toby,
There is a rarely used option "disable_local_bucket_check" in Riak CS.
I don't know it solves your case, please let me mention it.
To use it, first set it in app.config of riak-cs (or
application:set_env/3 in shell),
{riak_cs, [...
{disable_local_bucket_check, true},
Hi Andrew,
Thanks for the details.
The Puppet config should never have let it be setup with
allow_mult=false, but as this is a test cluster, it's possible
something went awry there at some point.
If it's not really a bug that needs reporting then I can let it go.
Thanks,,
Toby
On 7 July 2014 12:2
Hi Toby,
We've seen this scenario before. It occurs because riak-cs stores bucket
information in 2 places on disk:
1) Inside the user record (for bucket permissions)
2) Inside a global list of buckets, since each bucket must be unique
What has happened most likely is that the bucket is no lon
Hi,
At some point we've managed to create a couple of buckets that don't
work and can't be deleted (in a development/testing cluster, not
production).
They show up with both 's3cmd ls' or by querying the HTTP API for a
user's buckets.
However attempting to list files in the bucket, or removing the
