Aggregate "The lease ID specified did not match the lease ID for the blob" causes false alarms about azure-functions-eventhubs-extension HOT 7 CLOSED

We can you use this github item for the bug.

We need to add AggregateExceptioncheck in ProcessErrorAsync for LeaseLostException and ReceiverDisconnectedException and log the exceptions as information

from azure-functions-eventhubs-extension.

I'm running into something similar lately. According to this answer I don't think this is something you should worry about. This is mostly caused by the auto scaling.

from azure-functions-eventhubs-extension.

Thanks - @wenyi189 - it looks exactly like that answer describes.

Although it does mention that they should only be warnings, not errors. So I guess the problem is mostly about how the AggregateExcception gets thrown.

Just to keep people updated, I did raise a support ticket with Azure. So we'll see what happens and feed back.

from azure-functions-eventhubs-extension.

We are treating LeaseLostException as information, such exceptions are expected:
https://github.com/Azure/azure-functions-eventhubs-extension/blob/dev/src/Microsoft.Azure.WebJobs.Extensions.EventHubs/Listeners/EventHubListener.cs#L151.

There is no check for System.AggregateException, that's why you saw errors.

from azure-functions-eventhubs-extension.

Thanks @alrod (sorry about the close- hit the wrong button on the train).

So if I understand it, this is a bug, because low severity (expected) exceptions are causing high severity aggregate exceptions.

Where's the best place to report/fix this?

from azure-functions-eventhubs-extension.

I can take a look if you accept external PRs?

(Thought I'd check first, as I can see there's quite a few that have been open for months, and it looks like most closed ones have come from Microsoft?)

from azure-functions-eventhubs-extension.

Closing due to inactivity.

from azure-functions-eventhubs-extension.