[
https://issues.apache.org/jira/browse/KAFKA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744252#comment-14744252
]
Edward Ribeiro commented on KAFKA-2515:
---------------------------------------
Ewen was able to simulate the bug with a simple config with two brokers,
adjusting message.max.bytes and replica.fetch.max.bytes. Then he created a
topic with replication factor 2 and used console producer to send data of
different sizes to test the output. Unfortunately KAFKA-2338 has been on hold
for the past two months so I am back to square 1. :( Gonna try to repro here
following Ewen's strategy, but let's keep in touch.
Regards,
> handle oversized messages properly in new consumer
> --------------------------------------------------
>
> Key: KAFKA-2515
> URL: https://issues.apache.org/jira/browse/KAFKA-2515
> Project: Kafka
> Issue Type: Sub-task
> Components: clients
> Reporter: Jun Rao
> Assignee: Onur Karaman
> Fix For: 0.9.0.0
>
>
> When there is an oversized message in the broker, it seems that the new
> consumer just silently gets stuck. We should at least log an error when this
> happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
