On Dec 23, 2010, at 9:34, Timo Nentwig wrote: > I was about to add a secondary index (which apparently failed) to existing > data. When I restarted the node it crashed (!) with:
It crashed because it ran out of heap space (2G). So I increased to 3.5G but after a whlie it's caught in full GC again. The node holds some 50G of data. So, if 3.5G isn't sufficient, how do I determine how much memory it's going to need and more important how can I cancel such indexing if I don't have enough memory available? Or did I hit some bug and should simply wait for rc3? > INFO 09:21:36,510 Opening /var/lib/cassandra/data/test/tracking.6b6579-tmp-e-1 > ERROR 09:21:36,512 Exception encountered during startup. > java.lang.ArithmeticException: / by zero ... > So, I deleted the file which let's cassandra to startup again (and starting > all over to build the secondary index). > > Since 0.7rc2 was too unstable I'm on SNAPSHOT from Dec 17.
