On 06/22/2011 10:03 PM, Edward Capriolo wrote: > I have not read the original thread concerning the problem you mentioned. > One way to avoid OOM is large amounts of RAM :) On a more serious note most > OOM's are caused by setting caches or memtables too large. If the OOM was > caused by a software bug, the cassandra devs are on the ball and move fast. > I still suggest not jumping into a release right away.
For what it's worth that particular thread was about the kernel oom killer, which is a good example of a the kind of gotcha that has caused several people to chime in with the importance of monitoring both Cassandra and the OS.
