Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> unclean shutdown


Copy link to this message
-
Re: unclean shutdown
Just deleting the index files should fix this issue.
On Mon, Oct 14, 2013 at 5:23 PM, Kane Kane <[EMAIL PROTECTED]> wrote:

> Thanks a lot Neha, so I have to delete only index files not log files
> themselves? What is better way to do that?
>
>
> On Mon, Oct 14, 2013 at 4:52 PM, Neha Narkhede <[EMAIL PROTECTED]
> >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 <[EMAIL PROTECTED]>
> 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.
> > >
> >
>

 
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