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

[BUG] Eventhub SDK 5.10.0 stops reading Partitions #24426

Closed
the-mod opened this issue Sep 28, 2021 · 6 comments
Closed

[BUG] Eventhub SDK 5.10.0 stops reading Partitions #24426

the-mod opened this issue Sep 28, 2021 · 6 comments
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Hubs needs-author-feedback Workflow: More information is needed from author to address the issue. no-recent-activity There has been no recent activity on this issue.

Comments

@the-mod
Copy link

the-mod commented Sep 28, 2021

Describe the bug
I am using EventProcessorClient from azure-messaging-eventhubs:5.10.0 together with azure-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:

new EventProcessorClientBuilder()

.connectionString(connString)

.consumerGroup(cg)

.checkpointStore(new BlobCheckpointStore(containerClient))

.loadBalancingUpdateInterval(Duration.ofSeconds(5))

.partitionOwnershipExpirationInterval(Duration.ofSeconds(20))

.loadBalancingStrategy(LoadBalancingStrategy.GREEDY)

.processEventBatch(consumer, batchSize)

.processError(errorConsumer)

.processPartitionInitialization(initConsumer)

.processPartitionClose(closeConsumer)

.buildEventProcessorClient();

Expected behavior
Run for ever and ever

Setup (please complete the following information):

  • OS: Windows
  • Library/Libraries: azure-messaging-eventhubs:5.10.0 and azure-messaging-eventhubs-checkpointstore-blob:1.9.0
  • Java version: azul JRE 16
  • App Server/Environment: Tomcat 9.0.52
  • Frameworks: Spring Boot 2.4.10
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Sep 28, 2021
@the-mod the-mod changed the title [BUG] Eventhub SDK 5.10 stops working on Partitions [BUG] Eventhub SDK 5.10.0 stops reading Partitions Sep 28, 2021
@joshfree joshfree added Client This issue points to a problem in the data-plane of the library. Event Hubs labels Sep 28, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 28, 2021
@joshfree
Copy link
Member

@conniey could you follow up with @the-mod on this Event Hubs ReactorDispatcher instance is closed issue?

/cc @anuchandy

@conniey
Copy link
Member

conniey commented Sep 29, 2021

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

@the-mod
Copy link
Author

the-mod commented Sep 30, 2021

@conniey unfortunately nothing more than that in the timerframe some readers stopped working

@paalkristian
Copy link

We are experiencing this behavior as well. We are using azure-messaging-eventhubs:5.10.0 with azure-spring-cloud-stream-binder-eventhubs:2.8.0, which is using azure-messaging-eventhubs-checkpointstore-blob:1.9.0. Our application runs without problems between 4 and 14 days, before some messages are no longer consumed.

When I restart the consumer it works as expected again. I might be able to provide logs if it helps.

@conniey
Copy link
Member

conniey commented Oct 7, 2021

@paalkristian Hey. Providing logs would help because the end result of most bugs is that it stops receiving, but the cause is often different.

@conniey conniey added bug This issue requires a change to an existing behavior in the product in order to be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Nov 3, 2021
@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Nov 3, 2021
@conniey conniey added needs-author-feedback Workflow: More information is needed from author to address the issue. and removed needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team labels Jan 14, 2022
@ghost ghost added the no-recent-activity There has been no recent activity on this issue. label Jan 22, 2022
@ghost
Copy link

ghost commented Jan 22, 2022

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!

@ghost ghost closed this as completed Feb 5, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Hubs needs-author-feedback Workflow: More information is needed from author to address the issue. no-recent-activity There has been no recent activity on this issue.
Projects
None yet
Development

No branches or pull requests

5 participants