You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/08 20:22:26 UTC

[jira] [Commented] (STORM-692) KakfaSpout storage of offsets in Zookeeper lost

    [ https://issues.apache.org/jira/browse/STORM-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949088#comment-14949088 ] 

ASF GitHub Bot commented on STORM-692:
--------------------------------------

Github user d2r commented on the pull request:

    https://github.com/apache/storm/pull/447#issuecomment-146644441
  
    @rmkellogg, STORM-692 was resolved by you as invalid.  Would you close this pull request?


> KakfaSpout storage of offsets in Zookeeper lost
> -----------------------------------------------
>
>                 Key: STORM-692
>                 URL: https://issues.apache.org/jira/browse/STORM-692
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka
>    Affects Versions: 0.9.3
>            Reporter: Rick Kellogg
>            Assignee: Rick Kellogg
>
> Constructor for SpoutConfig and inadequate documentation in storm-kafka/README.md leads to lost persistence of Kafka offset information.
> The SpoutConfig class constructor takes four parameters:
> hosts - Zookeeper host & root path for Kafka 
> topic - Kafka topic name
> zkRoot - Zookeeper path for Kafka Spout offset
> id -- Identifier for KafkaSpout 
> Unfortunately it also exposes two public instance variables that must also be set: zkServers & zkPort.  If these two variables are not set it uses Storm default values(localhost & 2000) which cause the offset information to be lost.
> Suggest we replace the existing constructor with one that supplies all 6 required values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)