Hi Carlo, Can you post steps to reproduce over on https://issues.apache.org/jira/browse/CASSANDRA-3819 ? We have tried and failed to cause this problem.
On Thu, Jan 26, 2012 at 6:24 AM, Carlo Pires <carlopi...@gmail.com> wrote: > I found out this is related to schema change. Happens *every time* I create > drop and new CF with composite types. As workaround I: > > * never stop all nodes together > > To stop a node: > * repair and compact a node before stopping it > * stop and start it again > * if it started fine good if not, remove all data and restart the node (and > wait...) > > > 2012/1/25 aaron morton <aa...@thelastpickle.com> >> >> There is someone wrong with the way a composite type value was serialized. >> The length of a part on disk is not right. >> >> As a work around remove the log file, restart and then repair the node. >> >> How it got like that is another question. What was the schema change ? >> >> Cheers >> >> > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
