GitHub user abhishekagarwal87 opened a pull request:

    https://github.com/apache/storm/pull/1026

    STORM-1455: Do not reset the emittedOffset for offsetOutOfRangeExceptions

    There are two changes in this PR 
    
    - If there is a TopicOffsetOutOfRangeException, it can be due to an old 
failed tuple. We should not reset the state back to the beginning. 
    - Apart from the last completed offset, also emit the last emitted offset 
in the metric. latestEmittedOffset now points to the last emitted offset. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/abhishekagarwal87/storm kafka-spout

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/1026.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1026
    
----
commit c1e8ec576a391c9431ec50eb8eb60c083417b4c7
Author: Abhishek Agarwal <[email protected]>
Date:   2016-01-19T16:13:22Z

    STORM-1455: Do not reset the emittedOffset for offsetOutOfRangeExceptions

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to