[jira] [Updated] (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:all-tabpanel ] Jeremy Hanna updated CASSANDRA-8817: Complexity: Low Hanging Fruit > 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 > Environment: Ubuntu 14.04, VM originally created with 1 GB RAM, DSE > 4.6.0 installed >Reporter: Michael DeHaan >Priority: Low > 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 " or something similar would be a possible solution. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (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:all-tabpanel ] Philip Thompson updated CASSANDRA-8817: --- Issue Type: Improvement (was: Bug) 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)
[jira] [Updated] (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:all-tabpanel ] Michael DeHaan updated CASSANDRA-8817: -- Priority: Minor (was: Major) 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: Bug Components: Core Environment: Ubuntu 14.04, VM originally created with 1 GB RAM, DSE 4.6.0 installed Reporter: Michael DeHaan Priority: Minor Fix For: 2.1.3 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)
[jira] [Updated] (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:all-tabpanel ] T Jake Luciani updated CASSANDRA-8817: -- Fix Version/s: (was: 2.1.3) 2.1.4 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: Bug 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)
[jira] [Updated] (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:all-tabpanel ] T Jake Luciani updated CASSANDRA-8817: -- Labels: lhf (was: ) 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: Bug 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)
