Ok, so yeah it doesn't sound like that is what happened. on this partition.
FWIW all other 8 partitions were fine.

What I ended up doing was deleting partition N + all partitions > N (which
was about ~1 hour of data, given we just had a 8 hour outage this seemed

I can take a copy of the logs and try to search through them to find out
what happened. For future reference is there a way to force the kafka
server to perform recovery on all the segments?

If there had been a main() I could have run on the file to perform recovery
manually that would have been superb, not sure how easy that would be to
wire up?
On Sat, Apr 13, 2013 at 1:32 PM, Jay Kreps <[EMAIL PROTECTED]> wrote:
Matthew Rathbone
Foursquare | Software Engineer | Server Engineering Team
[EMAIL PROTECTED] | @rathboma <http://twitter.com/rathboma> |

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