-
Notifications
You must be signed in to change notification settings - Fork 59
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
Host suddenly stops receiving new messages without recovering #377
Comments
That's right #373 - fixes this issue. |
Great! I have changed to |
@royyeah - if you enable warn level logs for EventHub client package (along with EPH) - you would see these errors in the EventHub client logs |
@SreeramGarlapati - thanks, I will keep an eye on it. |
Thanks a lot for |
We encountered a similar error on two partitions and from the logs / data we are missing its seems both partitions never recovered (Java client I am not able to reopen the issue, apparently if you are not a collaborator on GitHub you can only reopen issues you closed yourself. Can you reopen the issue? Logs regarding error on partition 12:
Logs regarding error on partition 10:
Logs containing
Please let me know if you need more info (full logs for example). |
@royyeah - thanks a lot for reporting the issue and presenting the logs. |
@SreeramGarlapati - great, thanks, I will try the new version and let you know if I see it again. |
shouldn't the eph also be released with the newer dependency if this fixes this bug? i am also experiencing the same behaviour |
Actual Behavior
I am using an EventProcessorHost with basic setup as explained here. Recently we ran into problems where the host stops receiving new messages because it did not recover correctly. When we restarted the application it continued processing again.
Expected Behavior
I think the warnings below are the result of event hub partitions being moved across nodes. I would expect the event processor host to automatically recover from this.
Is this fixed in azure-eventhubs 1.1.0? I see this contains bugfixes #372 and #373 which sound like potential fixes.
Versions
More details
Log excerpt:
The text was updated successfully, but these errors were encountered: