Hi Luke,
Thanks for the response.
I played around with the various config options - and in the end I had to
include the /etc/defaults/riak file, as well as the
/etc/security/limits.conf config in order to get Riak to stay up. That must
be relatively new - our existing v1.4.0 cluster is operating
Hi Matt -
Can you attach to a node in your cluster with "riak attach" and run
this erlang snippet (before the node errors out)?
os:cmd("ulimit -n").
This will show the actual value for ulimit for that running riak node.
I suspect that this value hasn't been updated for the running process,
even
Hey list,
We're migrating from our currently operational cluster to a new one in a
different EC2 region. As part of this migration, we'd like to move from
Bitcask to eLevelDB - mostly for the benefits provided by secondary indexes.
We also use Multi-backend configuration, in order to split our va
