You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sumod Pawgi (JIRA)" <ji...@apache.org> on 2015/03/12 06:31:38 UTC
[jira] [Comment Edited] (CASSANDRA-8817) Error handling in
Cassandra logs in low memory scenarios could use improvement
[ https://issues.apache.org/jira/browse/CASSANDRA-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358123#comment-14358123 ]
Sumod Pawgi edited comment on CASSANDRA-8817 at 3/12/15 5:31 AM:
-----------------------------------------------------------------
Are you starting the node as only Cassandra or Analytical or Search? Please provide more information. DSE doc says that for light workloads C* can run on as low as 256 MB but it does not cover DataStax Enterprise, for which best practices are at - http://www.datastax.com/wp-content/uploads/2014/04/WP-DataStax-Enterprise-Best-Practices.pdf
was (Author: spawgi):
How much RAM are you using? Are you starting the node as only Cassandra or Analytical or Search? Please provide more information.
> Error handling in Cassandra logs in low memory scenarios could use improvement
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-8817
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8817
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: Ubuntu 14.04, VM originally created with 1 GB RAM, DSE 4.6.0 installed
> Reporter: Michael DeHaan
> Priority: Minor
> Labels: lhf
> Fix For: 2.1.4
>
>
> When running Cassandra with a low amount of RAM, in this case, using DataStax Enterprise 4.6.0 in a reasonably default configuration, I find that I get an error after starting and trying to use nodetool, namely that it cannot connect to 127.0.0.1. Originally this sends me up a creek, looking for why Cassandra is not listening on 7199. The truth ends up being a bit more cryptic - that Cassandra isn't running.
> Upon looking at the Cassandra system logs, I see the last thing that it did was print out the (very long) class path. This confused me as basically I'm seeing no errors in the log at all.
> I am proposing that Cassandra should check the amount of available RAM and issue a warning in the log, or possibly an error, because in this scenario Cassandra is going to oomkill and probably could have predicted this in advance.
> Something like:
> "Found X MB of RAM, expecting at least Y MB of RAM, Z MB recommended, may crash, adjust <SETTINGS>" or something similar would be a possible solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)