Hi Cassandra Devs,
After trying to setup the same settings (and importing same data)
to the 3 VMs on the same machine instead of 3 physical machines,
so far I couldn't replicate the exploded-commitlog situation.
On my 4-physical-machine setting, everything seems to be
back to normal (commitlog
Hi Cassandra Devs,
I intended to reduce the size of the db by the following steps:
1. removing all keys from one cf (somehow I can get all keys from the cf).
2. run nodetool cleanup on that cf one-node-by-one-node.
the size of the cf on one node is about 150 G,
I've made another cf with the
Some people (myself included) have seen issues when upgrading from 1.1.2
to 1.1.6 with tombstoned rows in the HintsColumnFamily
Some (mysql included) have fixed this by doing a
nodetool scrub system HintsColumnFamily
-mike
On 11/24/12 7:37 AM, Chuan-Heng Hsiao hsiao.chuanh...@gmail.com wrote:
Sorry, auto correct changed 'myself' to 'mysql'. Sorry for the confusion...
On Nov 24, 2012, at 9:29 AM, Michael Kjellman mkjell...@barracuda.com wrote:
Some people (myself included) have seen issues when upgrading from 1.1.2
to 1.1.6 with tombstoned rows in the HintsColumnFamily
Some
Hi Mike and Cassandra Devs,
It seems like the reason was because I was trying to
cleanup 2 CFs at the same time.
The scrub command successfully snapshoot HintsColumnFamily,
but seems hanged also (maybe because I did not stop cleanup.)
I ended up restarting the node, and redoing the cleanup
