Yes. 2.1 commitlogs are 8gb. 2.0 were 1gb. you can configure this in the yaml.
http://docs.datastax.com/en/cassandra/1.2/cassandra/configuration/configCassandra_yaml_r.html?scroll=reference_ds_qfg_n1r_1k__commitlog_segment_size_in_mb All the best, [image: datastax_logo.png] <http://www.datastax.com/> Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] <https://www.linkedin.com/company/datastax> [image: facebook.png] <https://www.facebook.com/datastax> [image: twitter.png] <https://twitter.com/datastax> [image: g+.png] <https://plus.google.com/+Datastax/about> <http://feeds.feedburner.com/datastax> <http://cassandrasummit-datastax.com/> DataStax is the fastest, most scalable distributed database technology, delivering Apache Cassandra to the world’s most innovative enterprises. Datastax is built to be agile, always-on, and predictably scalable to any size. With more than 500 customers in 45 countries, DataStax is the database technology and transactional backbone of choice for the worlds most innovative companies such as Netflix, Adobe, Intuit, and eBay. On Fri, May 22, 2015 at 6:51 AM, Ali Akhtar <ali.rac...@gmail.com> wrote: > I have a single node c* server (used for dev). I've been playing around > with it, inserting / removing several million rows. At the moment, all > tables have been dropped / truncated, and the data directory itself is > showing about 45mb used (most of it is probably in the OpsCenter tables > rather than mine). > > However, the commitlog directory shows a size of 8.1g. Is that really > normal? If this keeps up, I may run out of disk space due to the size of > the commit log rather than because of data. > > I have run nodetool compact, but it didnt bring down the size. >
