CODEWITHSUNDEEP
azureazure-functionsazure-eventhub
daz-fuller
daz-fuller

Reputation: 1231

Azure Function - Event Hub Trigger stopped

I've got an Azure Function app in production on an event hub trigger, it's low throughput with the function typically only being triggered once daily. It's running on an S1 plan at the moment and has a few other functions such as timer triggered and HTTP triggered.

It's been running fine but today it stopped being triggered by new messages until I restarted the app. All other functions were working just fine and responding to their associated triggers.

I've look through App Insights and there are no reported errors or issues, it's just not doing anything.

Has anyone else had this issue or know of what may be causing it?

Upvotes: 1

Views: 1551

Answers (1)

kamil-mrzyglod
kamil-mrzyglod

Reputation: 5008

First of all - is your App Service has Always On enabled?

Second thing - have you tried to test your trigger locally, so you can be sure, that there are no issues with your Event Hub?

Personally, I faced such issues when Event Host Processor implemented in EventHubTrigger was losing a lease because of additional processor introduced. It is also possible, that since it faces a low throughput, it lost a lease and for some reason was not able to renew it:

As an instance of EventProcessorHost starts it will acquire as many leases as possible and begin reading events. As the leases draw near expiration EventProcessorHost will attempt to renew them by placing a reservation. If the lease is available for renewal the processor continues reading, but if it is not the reader is closed and CloseAsync is called - this is a good time to perform any final cleanup for that partition.

https://blogs.msdn.microsoft.com/servicebus/2015/01/21/event-processor-host-best-practices-part-2/

Nonetheless, it is worth to contact the support to make sure there were no other issues.

Upvotes: 1

Related Questions