[
https://issues.apache.org/jira/browse/STORM-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-2611.
----------------------------------
Resolution: Won't Fix
Storm 1.x isn't maintained anymore.
> a batched kafkaspout with offsets in zookeeper
> ----------------------------------------------
>
> Key: STORM-2611
> URL: https://issues.apache.org/jira/browse/STORM-2611
> Project: Apache Storm
> Issue Type: Improvement
> Components: examples
> Affects Versions: 1.1.0
> Environment: Kafka, storm, zookeeper
> Reporter: lilizhi
> Priority: Trivial
> Labels: features, newbie
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> There are some issues with org.apache.storm.kafka.spout.KafkaSpout.
> 1. When the topology is running in multi workers in different supervisors, it
> is very often to trigger kafkaspout rebalance. And so the streaming is not
> stable. And it will cause massive retransmission of lost packets.
> 2. When max.uncommitted.offsets is less than 200000 (for limited flow),
> sometimes there is deadlock. The phenomenon is the heartbeat between spout
> and kafka can not be performed.
> 3. When the data is from storm to hbase, batch is used to improve writing
> productivity. So using batch from spout to bolt is better for special scene.
> 4. So a batched kafkaspout and bolt with offsets in zookeeper will be
> valuable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
