Share via

Using floating eventhub consumer groups

Deeksha Thakur 41 Reputation points Microsoft Employee
2022-02-28T08:26:15.577+00:00

I have 10 instance of same application reading data from Eventhub, however I want to assign them separate consumer group so that they do not interfere in each other's read and process simultaneously. Each application maintaining its own checkpointing in its local storage.

If I assign a consumer group randomly to the 10 instances(at the time of deployment or update), can they still read the right data based on their local checkpoint.

[Something like floating consumer group but fixed checkpoints? I nowhere did I see checkpoint as a property of consumer group?]

Azure Event Hubs

Answer accepted by question author

ShaikMaheer-MSFT 38,631 Reputation points Microsoft Employee Moderator
2022-03-21T09:34:26.667+00:00

Hi @Deeksha Thakur ,

I checked with internal team on this and below is the response from PG team. Kindly check.

So long as they know which partition and can specify a location in the event stream (offset/sequence number/timestamp), the consumer group shouldn't matter. There are a couple of caveats to be aware of:
• They won't be able to use one of our event processor types to read events without the consumer group becoming significant
• They won't be able to consume checkpoint data that our event processors have emitted without knowing the specific consumer group that was used
• They won't be able to request exclusive access to a partition unless they intend to prevent any other readers in that consumer group from accessing the partition
Outside of those considerations, I don't think there's a blocker to the proposed approach.

Hope this helps.

---------
Please consider hitting Accept Answer. Accepted answers helps community as well.

Was this answer helpful?


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.