Return-Path: 
 <commits-return-135150-apmail-cassandra-commits-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-commits-archive@www.apache.org
Delivered-To: apmail-cassandra-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E46F8189A9
	for <apmail-cassandra-commits-archive@www.apache.org>;
 Thu, 18 Jun 2015 15:11:43 +0000 (UTC)
Received: (qmail 73974 invoked by uid 500); 18 Jun 2015 15:11:43 -0000
Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org
Received: (qmail 73933 invoked by uid 500); 18 Jun 2015 15:11:43 -0000
Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@cassandra.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@cassandra.apache.org>
List-Post: <mailto:commits@cassandra.apache.org>
List-Id: <commits.cassandra.apache.org>
Reply-To: dev@cassandra.apache.org
Delivered-To: mailing list commits@cassandra.apache.org
Received: (qmail 73922 invoked by uid 99); 18 Jun 2015 15:11:43 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jun 2015 15:11:43 +0000
Date: Thu, 18 Jun 2015 15:11:43 +0000 (UTC)
From: "Gary Dusbabek (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12775733.1424206962000.109935.1434640303246@Atlassian.JIRA>
In-Reply-To: <JIRA.12775733.1424206962000@Atlassian.JIRA>
References: <JIRA.12775733.1424206962000@Atlassian.JIRA>
 <JIRA.12775733.1424206962258@arcas>
Subject: [jira] [Commented] (CASSANDRA-8817) Error handling in Cassandra
 logs in low memory scenarios could use improvement
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/CASSANDRA-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591945#comment-14591945 ] 

Gary Dusbabek commented on CASSANDRA-8817:
------------------------------------------

What would be appropriate levels for Y and Z?

> 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.x
>
>
> 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)