Today we are pleased to release Riak KV 2.2.1. Riak KV 2.2.1 is the latest
bugfix release, and continues Basho’s commitment to our customers and community
to develop and deliver a highly resilient, high-performance, key-value
database. Information about the specific fixes in this release can be
> Thanks for taking the time to look into this Luke. I should have asked
more questions when I setup the configuration for leveldb backend since
there is no clear documentation for how configure CS with leveldb only.
The reason for this is that a leveldb-only configuration is neither
supported nor
Thanks for taking the time to look into this Luke. I should have asked more
questions when I setup the configuration for leveldb backend since there is
no clear documentation for how configure CS with leveldb only.
In your current configuration, you are not using the expected prefix for
> the bloc
Done. Here it is: https://github.com/basho/riak_cs/issues/1333
2017-03-08 16:21 GMT+01:00 Jon Brisbin :
> Might be good to make sure this info is encapsulated into a GitHub issue
>> so we don't loose track of it.
>>
>>
>> In the end, the ONE thing to fix is the cumbersome error message. A
>> prop
>
> Might be good to make sure this info is encapsulated into a GitHub issue
> so we don't loose track of it.
>
>
> In the end, the ONE thing to fix is the cumbersome error message. A propre
> error message would have saved me days of "work"...
> Should I create a new issue for that ?
>
Please do.
2017-03-08 15:53 GMT+01:00 Jon Brisbin :
> FWIW- All work done so far on Riak-in-Docker is for purposes of testing
> and ad-hoc cluster creation and NOT for use in "production" environments
> (for any definition of the word "production"). Things like exposing the
> conf files on a volume which are
FWIW- All work done so far on Riak-in-Docker is for purposes of testing and
ad-hoc cluster creation and NOT for use in "production" environments (for
any definition of the word "production"). Things like exposing the conf
files on a volume which are more production-oriented haven't been in scope
of
Hello,
I finally found the problem : the riak and riak-cs config files where
stored in my app container, not in my persistent data container (where the
riak data is).
Whenever I upgraded the app container to a newly generated one, the conf
files and especially the admin user credentials did not ma
On 6 March 2017 at 03:49, Toby Corkindale wrote:
>
> I tried quite hard to get Riak to work reliably in a Docker container, in
a long-term-use kind of way.
> Riak would never shutdown cleanly, though, and so at startup there would
always be lots of lock files left around that had to be deleted fir
