Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Event Hubs] Ensure both batching and streaming receivers are able to re-establish links on retryable errors #3310

Closed
ramya-rao-a opened this issue May 30, 2019 · 1 comment
Closed

[Event Hubs] Ensure both batching and streaming receivers are able to re-establish links on retryable errors #3310

ramya-rao-a opened this issue May 30, 2019 · 1 comment
Assignees
@ShivangiReja
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Milestone
Sprint 154

Comments

@ramya-rao-a
Copy link
Contributor

Both batching and streaming receiver should retry establishing the AMQP receiver link in the below cases. The re-established link should start from the checkpoint i.e the last event provided to the user

  • retryable receiver error
  • retryable session error
  • retryable connection error

We know this is done for streaming receiver. The same needs to be done for batching receiver as well
@ramya-rao-a ramya-rao-a added Client This issue points to a problem in the data-plane of the library. Event Hubs labels May 30, 2019
This was referenced May 30, 2019
Closed
Closed
@ramya-rao-a ramya-rao-a added this to the Sprint 154 milestone May 30, 2019
@AlexGhiondea AlexGhiondea mentioned this issue May 31, 2019
Closed
16 tasks
@ramya-rao-a ramya-rao-a mentioned this issue May 31, 2019
Closed
@ShivangiReja ShivangiReja self-assigned this Jun 3, 2019
@ramya-rao-a
Copy link
Contributor Author

Done with #3493

@ShivangiReja ShivangiReja mentioned this issue Jun 6, 2019
Merged
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ShivangiReja ShivangiReja

Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Projects
None yet
Milestone
Sprint 154
Development

No branches or pull requests
2 participants
@ramya-rao-a @ShivangiReja