kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Neha Narkhede <neha.narkh...@gmail.com>
Subject Re: uncontrolled shutdown
Date Fri, 01 Nov 2013 15:15:00 GMT
Jun,

I've seen this happen in the latest code in trunk, need to remember how to
reproduce it.

Thanks,
Neha
On Nov 1, 2013 7:59 AM, "Jun Rao" <junrao@gmail.com> wrote:

> Are you using the latest code in the 0.8 branch?
>
> Thanks,
>
> Jun
>
>
> On Fri, Nov 1, 2013 at 7:36 AM, Kane Kane <kane.isturm@gmail.com> wrote:
>
> > Neha, yes when i kill it with -9, sure I will file a bug.
> >
> > Thanks.
> >
> >
> > On Fri, Nov 1, 2013 at 3:43 AM, Neha Narkhede <neha.narkhede@gmail.com
> > >wrote:
> >
> > > When you say the Kafka dies, did you mean a kill -9 or kill -15 ? I
> agree
> > > that Kafka should try and delete/rebuild index files, but in this case,
> > it
> > > sounds like a bug. Can you file a JIRA?
> > >
> > > Thanks,
> > > Neha
> > >
> > >
> > > On Fri, Nov 1, 2013 at 1:51 AM, Kane Kane <kane.isturm@gmail.com>
> wrote:
> > >
> > > > When machine with kafka dies, most often broker cannot start itself
> > with
> > > > errors about index files being corrupt. After i delete them manually
> > > broker
> > > > usually can boot up successfully. Shouldn't kafka try to
> delete/rebuild
> > > > broken index files itself?
> > > >
> > > > Also this exception looks a bit weird:
> > > > java.lang.IllegalArgumentException: requirement failed: Corrupt index
> > > > found, index file
> > > > (/disk1/kafka-logs/benchmark-2/00000000000000385258.index) has
> non-zero
> > > > size but the last offset is 385258 and the base offset is 385258
> > > >
> > > > Thanks.
> > > >
> > >
> >
>

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