This issue was related to
http://riak-users.197444.n3.nabble.com/HTTP-Access-Log-Performance-Log-issues-td4031830.html#a4031849.
Basically, when HTTP logging was enabled, memory usage started to gradually
increase until the Riak cluster ran out of memory.
It looks like after Riak attempts to roll
This bug was causing the memory leak seen in
http://riak-users.197444.n3.nabble.com/Memory-Usage-keeps-increasing-td4031826.html.
I guess its because the logs were somehow being buffered in memory rather
than being flushed to disk?
Basho, is this a known issue?
--
View this message in contex
Hi,
I am trying to use the HTTP Access logging on my Riak cluster to log the
request information, and I'm running into some issues. When the cluster
starts up, it begins logging HTTP requests as expected. However, at the end
of the current hour, these logs cease to be written to. I imagine it is
t
I have the following properties set in my buckets:
{
props: {
allow_mult: false,
basic_quorum: false,
big_vclock: 1,
chash_keyfun: {
mod: "riak_core_util",
fun: "chash_std_keyfun"
},
dw: "quorum",
last_write_wins: true,
linkfun: {
Hi,
I am currently using an in-memory backend on Riak 1.4.8, and I am
experiencing a situation where my riak nodes gradually run out of memory.
My application handles a small amount of data (10s of MBs), and writes to
the same Riak buckets using the same keys again and again, so the number of
Key
