0ef4e (
https://issues.apache.org/jira/browse/KAFKA-188)
Thanks for your help Jay, it looks like we'll have to start the 0.7.1 ->
0.8 upgrade process sooner than I thought.
On Wed, Jul 17, 2013 at 12:32 PM, Blake Smith wrote:
> 1. Cool. For now I'll write this off as a fluke si
t; messages about recovering each topic). This process goes through each
> message sequentially and checks the CRC. If that did happen it is unlikely
> that there was a problem in the log itself.
>
> -Jay
>
>
> On Tue, Jul 16, 2013 at 3:04 PM, Blake Smith >wrote:
>
> &
gment--in other
> words flushed data became corrupt. This is not handled in 0.7. In 0.8 you
> would have the option of just deleting the problematic data and restoring
> from replicas.
>
> -Jay
>
>
> On Tue, Jul 16, 2013 at 1:10 PM, Blake Smith >wrote:
>
> > H
Hi everyone,
Last week, one of our production Kafka 0.7.1 servers had a hardware failure
that resulted in an unclean restart. When the server came back up 5 minutes
later, there were two topic corruption problems that we had to handle to
get the pipeline working again.
1. The kafka log directory
