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.

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

Fix event hubs "quota exceeded" exceptions #245

Closed
sebastianburckhardt opened this issue Apr 10, 2023 · 1 comment
Closed

Fix event hubs "quota exceeded" exceptions #245

sebastianburckhardt opened this issue Apr 10, 2023 · 1 comment
Assignees

Comments

@sebastianburckhardt
Copy link
Member

In some cases Netherite users have seen exceptions like the following:

Microsoft.Azure.EventHubs.QuotaExceededException: Exceeded the maximum number of allowed receivers per partition in a consumer group which is 5.

There appear to be multiple reasons that contribute to this. Both of these issues should be investigated and fixed.

  • The client hash algorithm does not retry, nor generate a useful error message, when there are more than 5 clients in a bucket, which can happen. I saw in traces that even with 128 hash buckets, it may take only 256 elements to cause exhaustion due to normal imbalance. Thus we need to deal with this case better. For example, we can change the client id and retry.

  • EH clients are shutdown late in the shutdown process, which appears to sometimes hang, causing clients to not be released. Thus the number of "live" clients can be much larger than the number of nodes in the system. We should (a) shut down clients sooner, and (b) investigate and fix the underlying causes for the hangs.

@sebastianburckhardt
Copy link
Member Author

The second part of the solution to this issue (i.e. doing retries with a different client ID) is now implemented as part of PR #283.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant