Open oising opened 3 years ago
Assign me, @ReubenBond -- I thought maybe @benjaminpetit was going to do it, but if it's going to hang around the backlog, I'll find the time. Ben, if you're okay with this approach, I'd like to do it so I can get this into a release soon as it will make me feel a lot better about our production...
I haven't asked @benjaminpetit about it, I just figured this would be a good contribution. I didn't realize I could assign you directly :)
I appreciate it, by the way
I appreciate it, by the way
It's not entirely a selfless act ;)
We are always open to contribution @oising :)
We already have a EventHubReceiverOptions.StartFromNow
, maybe we could treat this case with the same setting?
Sure @benjaminpetit - if you'd prefer that, no problem.
@ReubenBond - which branch should I base the PR on? 3.x or main?
@oising main, and we can backport to 3.x
Putting this here for further reference: Azure/azure-sdk-for-net#28244
We've moved this issue to the Backlog. This means that it is not going to be worked on for the coming release. We review items in the backlog at the end of each milestone/release and depending on the team's priority we may reconsider this issue for the following milestone.
It's possible for checkpoint offset(s) to become invalid when the pulling agents are offline and partition data in the event hub is expunged/expired. When this happens, one or more pulling agent(s) is/are suspended - and exceptions repeatedly thrown - until their data in the storage account table is cleared.
I would suggest that the pulling agent(s) reset their position, following the pattern used by
EventProcessorOptions.InitialOffsetProvider
-- e.g.This would give optional per-partition recovery control and maximum flexibility while reusing available classes in the event hub package.
Example issue: