Riak Memory Usage Constantly Growing

John E. Vincent lusis.org+riak-users at gmail.com
Tue Oct 2 11:22:49 EDT 2012

Forgot to paste this in the last email. We ARE seeing the long_gc
messages (but no large_heap):

erlang.log.3:10:43:21.406 [info] monitor long_gc <0.29654.5763>
erlang.log.3:12:50:06.214 [info] monitor long_gc <0.2047.5836>
erlang.log.3:14:39:06.280 [info] monitor long_gc <0.336.0>
erlang.log.3:14:44:45.888 [info] monitor long_gc <0.672.0>

On Tue, Oct 2, 2012 at 7:55 AM, Kelly McLaughlin <kelly at basho.com> wrote:
> John and Shane,
> I have been looking into some memory issues lately and I would be very interested in more
> information about your particular problems. If either of you are able to get some output
> from etop using the -sort memory option when you are having elevated memory usage it
> would be very helpful to see. I know that sometimes you get the connection_lost message
> when trying to use etop, but I have found that sometimes if you keep trying it may succeed
> after a few attempts.
> Are either of you using MapReduce? I see that John is using 2I. Shane, do you also use 2I?
> Finally, do you notice a lot of messages to the console or console log that have the either the
> phrase 'monitor large_heap' or 'monitor long_gc'?
> Kelly

More information about the riak-users mailing list