You should be able to just bounce the broker. Our default policy is
that if we run out of space we shut down the broker automatically as
in that case there is no guarantee on what has been written to disk.
On startup if a clean shutdown hasn't been performed the broker should
run a recovery procedure on the log that includes checksumming all
messages. Invalid messages will be removed. Sounds like this isn't
what happened?


On Sat, Apr 13, 2013 at 10:30 AM, Matthew Rathbone
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB