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, and updated the schema on the affected CF so that the schema is saved with correct sstable compression options.
Huy -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/sstable-compression-chunk-length-kb-issue-tp7088773p7091638.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
