So will cassandra provide a way to limit its off-heap usage to avoid unexpected OOM kills?  I'd much rather have performance degrade when 100% of the index samples no longer fit in memory rather than the process being killed with no way to stabilize it without adding hardware or removing data.

-Bryan


On Fri, May 10, 2013 at 7:44 PM, Edward Capriolo <edlinuxguru@gmail.com> wrote:
If you use your off heap memory linux has an OOM killer, that will kill a random tasks.


On Fri, May 10, 2013 at 11:34 AM, Bryan Talbot <btalbot@aeriagames.com> wrote:
If off-heap memory (for indes samples, bloom filters, row caches, key caches, etc) is exhausted, will cassandra experience a memory allocation error and quit?  If so, are there plans to make the off-heap usage more dynamic to allow less used pages to be replaced with "hot" data and the paged-out / "cold" data read back in again on demand?