[
https://issues.apache.org/jira/browse/SAMZA-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629307#comment-16629307
]
ASF GitHub Bot commented on SAMZA-1914:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/664
> out of range starting offset for EH consumer
> --------------------------------------------
>
> Key: SAMZA-1914
> URL: https://issues.apache.org/jira/browse/SAMZA-1914
> Project: Samza
> Issue Type: Bug
> Reporter: Hai
> Assignee: Hai
> Priority: Major
>
> In EventHubs today we use offset + 1 as the next offset. This would cause
> problem if the consumer restarts and there is no event produced into the
> server. Because then offset + 1 would be an out of range offset and eventhubs
> client would fail to initialize.
> The proposed fix here is to always use offset (+0) as the "next" offset. And
> when we initialize the EH client, we specify to exclude the offset that we
> provide. This way we won't be reprocessing the last event and we avoid out of
> range offset error.
> We need to be careful that this doesn't cause Brooklin to miss event; so
> should also double check the EH connector in Brooklin as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
