Please review the minimum hardware requirements as clearly documented: http://docs.datastax.com/en/cassandra/3.x/cassandra/planning/planPlanningHardware.html
Please adjust your hardware usage to at least meet the clearly documented minimum requirements. If you continue to encounter problems once you have corrected your configuration error, please resubmit the details with updated hardware configuration details. Just to be clear, development on less than 4 GB is not supported and production on less than 8 GB is not supported. Those are not suggestions or guidelines or recommendations, they are absolute requirements. -- Jack Krupansky On Fri, Mar 4, 2016 at 9:04 PM, Hiroyuki Yamada <mogwa...@gmail.com> wrote: > Hi, > > I'm working on some POCs for Cassandra with single 2GB RAM node > environment and > some issues came up with me, so let me ask here. > > I have tried to insert about 200 million records (about 11GB in size) to > the node, > and the insertion from an application program seems completed, > but something (probably compaction?) was happening after the insertion and > later Cassandra itself was killed by OOM killer. > > I've tried to tune the configurations including heap size, compaction > memory setting and bloom filter setting > to make C* work nicely in the low memory environment, > but in any cases, it doesn't work so far. (which means I still get OOM > eventually) > > I know it is not very recommended to run C* in such low memory environment, > but I am wondering what can I do (what configurations to change) to make > it a little more stable in such environment. > (I understand the following configuration is very tight and not very > recommended but I just want to make it work now) > > Could anyone give me a help ? > > > Hardware and software : > - EC2 instance (t2.small: 1vCPU, 2GB RAM) > - Cassandra 2.2.5 > - JDK 8 (8u73) > > Cassandara configuraions (what I changed from the default) : > - leveledCompactionStrategy > - custom configuration settings of cassandra-env.sh > - MAX_HEAP_SIZE: 640MB > - HEAP_NEWSIZE: 128MB > - custom configuration settings of cassandra.yaml > - commitlog_segment_size_in_mb: 4 > - commitlog_total_space_in_mb: 512 > - sstable_preemptive_open_interval_in_mb: 16 > - file_cache_size_in_mb: 40 > - memtable_heap_space_in_mb: 40 > - key_cache_size_in_mb: 0 > - bloom filter is disabled > > > === debug.log around when Cassandra was killed by OOM killer === > DEBUG [NonPeriodicTasks:1] 2016-03-04 00:36:02,378 > FileCacheService.java:177 - Invalidating cache for > /var/lib/cassandra/data/test/user-adc91d20e15011e586c53fd5b957bea8/tmplink-la-15626-big-Data.db > DEBUG [NonPeriodicTasks:1] 2016-03-04 00:36:09,903 > FileCacheService.java:177 - Invalidating cache for > /var/lib/cassandra/data/test/user-adc91d20e15011e586c53fd5b957bea8/tmplink-la-15622-big-Data.db > DEBUG [NonPeriodicTasks:1] 2016-03-04 00:36:14,360 > FileCacheService.java:177 - Invalidating cache for > /var/lib/cassandra/data/test/user-adc91d20e15011e586c53fd5b957bea8/tmplink-la-15626-big-Data.db > DEBUG [NonPeriodicTasks:1] 2016-03-04 00:36:20,004 > FileCacheService.java:177 - Invalidating cache for > /var/lib/cassandra/data/test/user-adc91d20e15011e586c53fd5b957bea8/tmplink-la-15622-big-Data.db > ====== > > === /var/log/message === > Mar 4 00:36:22 ip-10-0-0-11 kernel: Killed process 8919 (java) > total-vm:32407840kB, anon-rss:1535020kB, file-rss:123096kB > ====== > > > Best regards, > Hiro > >
