We are running into KAFKA-1641 where the log cleaner thread dies with the below
INFO. Is there a work around for this issue? We are running kafka-0.9.0.
2017-09-18 16:12:41,621 INFO kafka.log.LogCleaner: Cleaner 0: Building offset
map for log __consumer_offsets-16 for 2149 segments in offset
restarted quickly
after that. Then, because of bad shutdown it takes a while to recover
unflushed segments.
My original question was to know if I should apply KAFKA-1641 patch to
0.8.2.1 release tag and if it was safe to do it. Any recommendation (other
than I will obviously upgrade to 0.8.2.1
I suppose that the patch for KAFKA-1641 had a fix for this issue.
Also it might be worth looking at Kafka-1755.
Thanks,
Mayuresh
On Fri, Mar 13, 2015 at 8:13 AM, Marc Labbe mrla...@gmail.com wrote:
No exactly, the topics are compacted but messages are not compressed.
I get the exact same
,
we're often seeing log cleaner exceptions reported in KAFKA-1641 and
I'd
like to know if it's safe to apply the patch from that issue resolution
to
0.8.2.1?
Reference: https://issues.apache.org/jira/browse/KAFKA-1641
Also there are 2 patches in there, I suppose
Did you get into that issue for the same reason as in the jira, i.e.,
somehow compressed messages were sent to the compact topics?
Thanks,
Jun
On Fri, Mar 13, 2015 at 6:45 AM, Marc Labbe mrla...@gmail.com wrote:
Hello,
we're often seeing log cleaner exceptions reported in KAFKA-1641 and I'd
into that issue for the same reason as in the jira, i.e.,
somehow compressed messages were sent to the compact topics?
Thanks,
Jun
On Fri, Mar 13, 2015 at 6:45 AM, Marc Labbe mrla...@gmail.com wrote:
Hello,
we're often seeing log cleaner exceptions reported in KAFKA-1641 and I'd
like to know
Hello,
we're often seeing log cleaner exceptions reported in KAFKA-1641 and I'd
like to know if it's safe to apply the patch from that issue resolution to
0.8.2.1?
Reference: https://issues.apache.org/jira/browse/KAFKA-1641
Also there are 2 patches in there, I suppose I should be using only
