We got the server to start up by applying the patch from the mentioned JIRA,
and modified the configuration parameters reader code to set
chunk_lenghth_size to null on start so that cassandra will use the default
value of 64k. We then deployed the code to the rest of the servers in the
cluster, a
Looks like this is related to bug in
https://issues.apache.org/jira/browse/CASSANDRA-3558.
Show schema shows sstable compression chunk_length_kb on the node that the
schame was applied is 65536, thought the schema update statement specified
chunk_length_kb=64, and on other nodes on the cluster
Hi,
We are running 1.0.3. I tried to restart a node, but it won't come up.
Below is the error logged:
INFO [SSTableBatchOpen:1] 2011-12-13 04:14:52,095 SSTableReader.java (line
134) Opening /u01/cassandra/data/system/HintsColumnFamily-hb-114 (66 bytes)
INFO [main] 2011-12-13 04:14:52,145 Datab
