[
https://issues.apache.org/jira/browse/KAFKA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952094#comment-14952094
]
Jun Rao commented on KAFKA-2515:
--------------------------------
The following is how you can reproduce this.
1. Create a new topic test3, allowing a larger message size.
kafka-topics --zookeeper localhost:2181 --create --topic test3 --partition
1 --replication-factor 1 --config max.message.bytes=1300000
2. Add one oversize message.
kafka-run-class org.apache.kafka.clients.tools.ProducerPerformance test3 1
1200000 1000 bootstrap.servers=localhost:9090,localhost:9091,localhost:9092
max.request.size=2000000
3. Consume messages on topic test3.
kafka-console-consumer --from-beginning --topic test3 --zookeeper
localhost:2181
> 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)
