Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-1914

out of range starting offset for EH consumer

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.0
    • None
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              lhaiesp Hai Lu
              lhaiesp Hai Lu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: