Hi together,
when I try to start my riak installation with the init-script, I run into the
following error message:
* root@unity-backend-dev:~# /etc/init.d/riak start
* [] Starting riak (via systemctl): riak.serviceFailed to start
riak.service: Unit riak.service failed to
Hi Karsten,
If Riak start works fine without init.d than it is great. It means that it is
working, it is just in another directory.
Ildar.
> 23 февр. 2015 г., в 13:12, Karsten Hauser написал(а):
>
> Hi together,
>
> when I try to start my riak installation with the init-script, I run into th
On 23 February 2015 at 10:12, Karsten Hauser wrote:
> Hi together,
>
>
>
> when I try to start my riak installation with the init-script, I run into
> the following error message:
>
>
>
> · root@unity-backend-dev:~# /etc/init.d/riak start
>
> · [] Starting riak (via systemctl
Hi Ildar,
Indeed, but I have integrated riak into my puppet configuration to simplify our
deployment. There the init.d-script will be called automatically. So just
calling “riak start” doesn’t work for me..
Best
Karsten
From: Ildar Alishev [mailto:ildaralis...@gmail.com]
Sent: Montag, 23. Feb
On 2/22/15 6:16 PM, Jason Campbell wrote:
Coming at this from another angle, if you already have a permanent data store,
and you are only reporting on each hour at a time, can you run the reports
based on the log itself?
A lot of Riak’s advantage comes from the stability and availability of dat
Hi there,
I can't seem to be able to get ACLs set properly on newly created buckets in
riak-cs. I am using s3curl to push the payload up via PUT /?acl and it returns
200 OK. However, a GET /?acl returns an xml payload with missing IDs. Without
manually pushing new ACLs, the default ACLs correc
Thanks for the info.
The model looks reasonable, but something I would worry about is the
availability of the key data. For example, the timestamps and msg-ids should
be known without key-listing Riak (which is always a very slow operation).
There is several options for this, you can either m
