Hi, all
I'm wondering is there any way to make a bucket in Riak-CS "public-write"?
i tried to call s3cmd:
s3cmd setacl --acl-public s3://test-bucket/
but it only make bucket's read public:
s3cmd info s3://test-bucket
Location: any
ACL: foobar: FULL_CONTROL
ACL: *anon*: READ
Hi, colleagues, please t ell me how to properly enable encryption between
nodes? I have only uncommented the following lines in vm.args:
-proto_dist inet_ssl
-ssl_dist_opt client_certfile "/etc/riak/cert.pem"
-ssl_dist_opt server_certfile "/etc/riak/cert.pem" ,
and got the error :
-
Hi,
It looks like you are trying to run Riak with Erlang R16B01. Version 1.4.2 of
Riak does not support this and requires Erlang R15B01 [0].
Best regards,
Christian
[0] http://docs.basho.com/riak/latest/ops/building/installing/rhel-centos/
On 4 Dec 2013, at 12:08, Игонин Михаил wrote:
> Hi
Christian, thank you! It looks like the truth...
Unfortunately, my application, that interacts with riak -- is already heavy
depends on the features of Erlang release 16. Maybe somebody knows a some
work-around?
With best regards,
Mike
Среда, 4 декабря 2013, 12:26 UTC от Christian Dahlqvi
Mike,
Your application should speak to Riak using the official client library (
github.com/basho/riak-erlang-client), not directly. That said, the option
you want is -proto_dist inet_tls, which was changed in R15 (or earlier, I
don't recall).
On Wed, Dec 4, 2013 at 7:18 AM, Игонин Михаил wrote:
Hi there,
I don't think s3cmd lets you set public-read-write on buckets. Probably for
a good reason, it is generally not a good idea :)
I have attached a quick patch against the latest s3cmd HEAD that should let
you do this. I tested it quickly, so use at your own risk :)
If you set the acl back
Alain,
Hi, I’m the author of riakpbc. I did some experimenting this morning and
discovered some rare cases that caused the connection timeout guard to be
created twice, which caused some interesting problems (i.e. the command could
succeed and the callback would be fired a second time with a ti
This same thing is happening to me, where both $bucket index and my own custom
indexes are returning keys that have been deleted and I can’t remove them.
I am hoping there is a way to fix this as it is causing significant problems
for us in production. It seems to be happening with some frequency
