[
https://issues.apache.org/jira/browse/STORM-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627501#comment-14627501
]
Sriharsha Chintalapani commented on STORM-869:
----------------------------------------------
[~sweetest_sj] this is not a issue with kafka spout . Its how the kafka api is
your fetch.max.message.bytes should always be higher than the max message size
.
you can check broker's server.properties message.max.bytes and make sure you
set fetch.max.message.bytes to equal or higher.
> kafka spout cannot fetch message if log size is above fetchSizeBytes
> --------------------------------------------------------------------
>
> Key: STORM-869
> URL: https://issues.apache.org/jira/browse/STORM-869
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka
> Affects Versions: 0.9.5
> Reporter: Adrian Seungjin Lee
> Priority: Critical
>
> let's say maxFetchSizeBytes is set to 1 megabytes, then if there exists a
> message that is bigger than 1 m, kafka spout just hangs and become inactive.
> This is both happening in Kafka spout for bolt/spout topology and also in
> trident spouts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
