Might be good to have a more friendly error message though!
On Thu, May 28, 2015 at 4:32 PM, Andrey Yegorov
wrote:
> Thank you!
>
> --
> Andrey Yegorov
>
> On Wed, May 27, 2015 at 4:42 PM, Jiangjie Qin
> wrote:
>
> > This should be just a message fetch failure. The socket was disconnect
Thank you!
--
Andrey Yegorov
On Wed, May 27, 2015 at 4:42 PM, Jiangjie Qin
wrote:
> This should be just a message fetch failure. The socket was disconnected
> when broker was writing to it. There should not be data loss.
>
> Jiangjie (Becket) Qin
>
> On 5/27/15, 11:00 AM, "Andrey Yegoro
This should be just a message fetch failure. The socket was disconnected
when broker was writing to it. There should not be data loss.
Jiangjie (Becket) Qin
On 5/27/15, 11:00 AM, "Andrey Yegorov" wrote:
>I've noticed a few exceptions in the logs like the one below, does it
>indicate data loss?
I've noticed a few exceptions in the logs like the one below, does it
indicate data loss? should I worry about this?
What is the possible reason for this to happen?
I am using kafka 0.8.1.1
ERROR Closing socket for /xx.xxx.xxx.xxx because of error
(kafka.network.Processor)
kafka.common.KafkaExcep
