-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[BUG] Eventhub SDK 5.10.0 stops reading Partitions #24426
Comments
@conniey could you follow up with @the-mod on this /cc @anuchandy |
Hey, the ReactorDispatcher instance is closed is misleading (and we plan on suppressing this because it isn't actually the cause of errors). I was wondering if you had any logs so we can see what happened before this exception. [edit] We did fix a bug this past two weeks where a graceful close from the service would result in the receives not resuming... I'd need to look at the logs to understand if its the issue you're running into though. #24141 |
@conniey unfortunately nothing more than that in the timerframe some readers stopped working |
We are experiencing this behavior as well. We are using When I restart the consumer it works as expected again. I might be able to provide logs if it helps. |
@paalkristian Hey. Providing logs would help because the end result of most bugs is that it stops receiving, but the cause is often different. |
Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you! |
Describe the bug
I am using
EventProcessorClient
fromazure-messaging-eventhubs:5.10.0
together withazure-messaging-eventhubs-checkpointstore-blob:1.9.0
to read Events from Eventhubs.The reading of Partitions stops out of sudden and does not recover.
This leads to the fact, Events on the affected Partitions are piling up.
Only a restart of the Application mitigates this Issues, but after some time it hit again and again.
Exception or Stack Trace
In the logs I see
ReactorDispatcher instance is closed
Exceptions coming from the SDK.Unfortunately no Stacktrace is provided
To Reproduce
Found no way to reproduce due to the fact it hit my Services at random uptime.
It seams also to be independent on the amount of Events read out by the App.
Code Snippet
This is my current way to init a EventProcessorClient:
Expected behavior
Run for ever and ever
Setup (please complete the following information):
azure-messaging-eventhubs:5.10.0
andazure-messaging-eventhubs-checkpointstore-blob:1.9.0
The text was updated successfully, but these errors were encountered: