kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jun Rao <jun...@gmail.com>
Subject Re: unclean shutdown
Date Tue, 15 Oct 2013 03:40:24 GMT
Is this issue reproducible?

Thanks,

Jun


On Mon, Oct 14, 2013 at 8:30 PM, Kane Kane <kane.isturm@gmail.com> wrote:

> Yes, my expectation would be that broker will try to restore or delete it
> itself.
>
>
> On Mon, Oct 14, 2013 at 5:55 PM, Sriram Subramanian <
> srsubramanian@linkedin.com> wrote:
>
> > Is this a bug? Can an unclean shutdown leave the index in a corrupt state
> > that the broker cannot start (expected state)?
> >
> > On 10/14/13 4:52 PM, "Neha Narkhede" <neha.narkhede@gmail.com> wrote:
> >
> > > It is possible that the unclean broker shutdown left the index in an
> > >inconsistent state. You can delete the corrupted index files, that will
> > >make the Kafka server rebuild the index on startup.
> > >
> > >Thanks,
> > >Neha
> > >
> > >
> > >On Mon, Oct 14, 2013 at 3:05 PM, Kane Kane <kane.isturm@gmail.com>
> wrote:
> > >
> > >> After unclean shutdown kafka reports this error on startup:
> > >> [2013-10-14 16:44:24,898] FATAL Fatal error during KafkaServerStable
> > >> startup. Prepare to shutdown (kafka.server.KafkaServerStartable)
> > >> java.lang.IllegalArgumentException: requirement failed: Corrupt index
> > >> found, index file
> > >>(/disk1/kafka-logs/perf2-22/00000000000000000000.index)
> > >> has non-zero size but the last offset is 0 and the base offset is 0
> > >>
> > >> How it's supposed to bring broker back after unclean shutdown?
> > >>
> > >> Thanks.
> > >>
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message