You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Adrian Seungjin Lee (JIRA)" <ji...@apache.org> on 2015/06/16 09:56:00 UTC
[jira] [Commented] (STORM-869) kafka spout cannot fetch message if
log size is above fetchSizeBytes
[ https://issues.apache.org/jira/browse/STORM-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587624#comment-14587624 ]
Adrian Seungjin Lee commented on STORM-869:
-------------------------------------------
You can reproduce this by setting fetchSizeBytes to reasonably small number, I think the default behavior should be modified to get at least one message from kafka, is it doable?
> 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)