This sounds like Kafka not being entirely robust to disk corruption, which
seems entirely possible and normal. I'd simply delete that log file and let
a replica replay catch it up at broker bootup.
Trying to guard against all possible disk corruption bugs sounds very
difficult to me, it seems bett
I'm not from the Kafka dev team so I won't be able to comment whether
this is an expected way to fail or if this needs to be handled in a more
cleaner/robust manner (at least very least probably a better exception
message). Since you have put in efforts to write a test case and narrow
it down t
Kafka version: 0.10.0
Exception Trace
java.util.NoSuchElementException
at kafka.utils.IteratorTemplate.next(IteratorTemplate.scala:37)
at kafka.log.LogSegment.recover(LogSegment.scala:189)
at kafka.log.Log.recoverLog(Log.scala:268)
at kafka.log.Log.loadSegments(Log.scala:243)
Can you paste the entire exception stacktrace please?
-Jaikiran
On Tuesday 30 August 2016 11:23 AM, Gaurav Agarwal wrote:
Hi there, just wanted to bump up the thread one more time to check if
someone can point us in the right direction... This one was quite a serious
failure that took down many
Hi there, just wanted to bump up the thread one more time to check if
someone can point us in the right direction... This one was quite a serious
failure that took down many of our kafka brokers..
On Sat, Aug 27, 2016 at 2:11 PM, Gaurav Agarwal
wrote:
> Hi All,
>
> We are facing a weird problem
Hi All,
We are facing a weird problem where Kafka broker fails to start due to an
unhandled exception while 'recovering' a log segment. I have been able to
isolate the problem to a single record and providing the details below:
During Kafka restart, if index files are corrupted or they don't exis
