Re: Cassandra 3.1.1 with respect to HeapSpace

Thank you Sebastián! On 15 Jan 2016, at 19:09 , Sebastian Estevez > wrote: The recommended (and default when available) heap size for Cassandra is 8GB and for New size it's 100mb per core. Your milage may vary based on

Re: Cassandra 3.1.1 with respect to HeapSpace

The recommended (and default when available) heap size for Cassandra is 8GB and for New size it's 100mb per core. Your milage may vary based on workload, hardware etc. There are also some alternative JVM tuning schools of thought. See cassandra-8150 (large heap) and CASSANDRA-7486 (G1GC). All

Re: Cassandra 3.1.1 with respect to HeapSpace

Thank you Sebastián for your useful advice. I managed restarting the nodes, but I needed to delete all the commit logs, not only the last one specified. Nevertheless I’m back in business. Would there be a better memory configuration to select for my nodes in a C* 3 cluster? Currently I use

Re: Cassandra 3.1.1 with respect to HeapSpace

How can I restart? It blocks with the error listed below. Are my memory settings good for my configuration? On 14 Jan 2016, at 18:30, Jake Luciani > wrote: Yes you can restart without data loss. Can you please include info about how much data you have

Re: Cassandra 3.1.1 with respect to HeapSpace

Ok, I will open a ticket. How could I restart my cluster without loosing everything ? Would there be a better memory configuration to select for my nodes? Currently I use MAX_HEAP_SIZE="6G" HEAP_NEWSIZE=“496M” for a 16M RAM node. Thanks Jean On 14 Jan 2016, at 18:19, Tyler Hobbs

Re: Cassandra 3.1.1 with respect to HeapSpace

Yes you can restart without data loss. Can you please include info about how much data you have loaded per node and perhaps what your schema looks like? Thanks On Thu, Jan 14, 2016 at 12:24 PM, Jean Tremblay < jean.tremb...@zen-innovations.com> wrote: > > Ok, I will open a ticket. > > How

Re: Cassandra 3.1.1 with respect to HeapSpace

I don't think that's a known issue. Can you open a ticket at https://issues.apache.org/jira/browse/CASSANDRA and attach your schema along with the commitlog files and the mutation that was saved to /tmp? On Thu, Jan 14, 2016 at 10:56 AM, Jean Tremblay < jean.tremb...@zen-innovations.com> wrote:

Re: Cassandra 3.1.1 with respect to HeapSpace

Try starting the other nodes. You may have to delete or mv the commitlog segment referenced in the error message for the node to come up since apparently it is corrupted. All the best, [image: datastax_logo.png] Sebastián Estévez Solutions Architect | 954 905 8615 |

Cassandra 3.1.1 with respect to HeapSpace

Hi, I have a small Cassandra Cluster with 5 nodes, having 16MB of RAM. I use Cassandra 3.1.1. I use the following setup for the memory: MAX_HEAP_SIZE="6G" HEAP_NEWSIZE="496M" I have been loading a lot of data in this cluster over the last 24 hours. The system behaved I think very nicely. It