Dinesh,
I took a look at your logs, first it seems error_logs_kafka_request.log is
also from the consumer side, not the server side.
And the error logs are pointing to an EOF on the server side while reading
the data, one possibility is that your socket buffer size is configured to
be not as
We don't have any compression on Kafka
On 14 January 2015 at 22:54, Guozhang Wang wangg...@gmail.com wrote:
Did you have compression enabled on Kafka?
On Tue, Jan 13, 2015 at 10:33 AM, dinesh kumar dinesh...@gmail.com
wrote:
We are using 0.8.1.1 version of Kafka and *not 0.8.2 *as
We are using 0.8.1.1 version of Kafka and *not 0.8.2 *as mentioned above.
Thanks,
Dinesh
On 13 January 2015 at 23:35, dinesh kumar dinesh...@gmail.com wrote:
Hi Guozhang,
Sorry for the misinformation. We have file sizes around 50 - 100 MB. So we
set *fetch.message.max.bytes* conservatively
Hi Guozhang,
Sorry for the misinformation. We have file sizes around 50 - 100 MB. So we
set *fetch.message.max.bytes* conservatively around 188743680. Can you
please explain me the reason for this behavior?
Thanks,
Dinesh
On 13 January 2015 at 21:42, Guozhang Wang wangg...@gmail.com wrote:
Dinesh,
Your fetch.message.max.bytes is 188743680 155MB, but you said some
messages can be as large as 180MB. Could you try to set it to be larger
than, say 200MB and see if it helps?
Guozhang
On Tue, Jan 13, 2015 at 4:18 AM, dinesh kumar dinesh...@gmail.com wrote:
Hi,
I am been facing some
