java.lang.Thread.run(Thread.java:662)
At which point broker actually dies. Shouldn't it keep working even even if
there is some such error?
Also, does anyone else saw this error? And is it fixed in the newer versions?
--
Dmitri Priimak
the way problem does go
away if I upgrade broker to version 0.7.1 or 0.7.2
--
Dmitri Priimak
Thanks,
Jun
On Wed, Nov 28, 2012 at 11:34 AM, Dmitri Priimak <
prii...@highwire.stanford.edu> wrote:
Hi.
In the kafka broker (version 0.7.0) log I see occasionally following error
message
Do you have a way to reproduce this issue ?
Sort of.
I see this bug report https://issues.apache.org/jira/browse/KAFKA-273 that says
"Unresolved"
and it shows the same stacktrace as the one I reported. However that comments
at the bottom
sounds like this issue might have been resol
ee. I will try to isolate this problem. I am hoping that I can locate exact
sequence of messages
that trigger this problem, but at the moment I cannot easily do that.
--
Dmitri Priimak
>
> Thanks,
> Neha
>
> On Thu, Nov 29, 2012 at 2:03 PM, Dmitri Priimak
> wrote:
>> On
Well, it does not look like I can reproduce it anymore. While I was able to
consistently crash it
yesterday, today kafka broker runs without any problems.
--
Dmitri Priimak
On 11/29/2012 02:10 PM, Dmitri Priimak wrote:
> On 11/29/2012 02:06 PM, Neha Narkhede wrote:
>> That just mean
would you recommend? Is "Snappy compression" any good?
--
Dmitri Priimak
On 11/30/2012 01:17 PM, Paul Sutter wrote:
> Any chance the stream was created by the gzip command? If so, that just
> happens sometime. The only
> way we found is to confirm that the error happened at the ex
