Closed ashamrai closed 1 year ago
@ashamrai : Kindly share us the Function App details privately, so that we can check the backend logs for your Application. Sharing-Your-Function-App-name-privately
Location: West Europe Failed run: timestamp [UTC] = 2022-12-07T13:08:42.6715745Z ; Id=43fd7050-2e14-487b-9aaa-cdf81fe6450d First retry: timestamp [UTC] = 2022-12-07T13:09:12.9488119Z; Id=b7cf4e13-fca6-404a-bcd0-73b7b738aa5a Second retry: timestamp [UTC] = 2022-12-07T13:09:12.9499934Z; Id=57c2717f-f02a-4734-80ff-e46d3ec6f240
@alrod please comment and validate on this.
@ashamrai what is eventhub extension verson?
pls update about eventhub version
@bhagyshricompany our configuration:
{
"version": "2.0",
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle",
"version": "[2.*, 3.0.0)"
}
}
@sidkri pls comment
@ashamrai Ican see function is still runing in problematic version. please go through this link which is updated for fixed. https://github.com/Azure/azure-functions-eventhubs-extension/issues/114
Thanks @bhagyshricompany for identifying the work around. @ashamrai please upgrade to extensions bundle v4 which uses the latest verison of the Event Hubs extension and SDK that does not have this logging issue: https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-register#extension-bundles Set the extensionBundle.version to "[4.0.0, 5.0.0)". Compile locally to ensure no code changes are needed.
Please close this issue once you have upgraded and no longer have the issue as we are tracking the logging issue via #144
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
As inheritor of https://github.com/Azure/Azure-Functions/issues/2310
Runtime version: ~4 Os: windows Hosting plan: consumption Language: java Trigger: Event Hub
When we receive "Did not find any initialized language workers", we expect retrying of failed function.
Example:
This is traces of the failed execution:
and we see the retries (line 2 and 3):
However, the first retry receives:
The second retry receives:
So... two executions with the same partition, offset, sequence number and enqueue time receive two different events.
Then I`ve tried to read this event through this simple code:
When I use
EventPosition eventPosition = EventPosition.FromSequenceNumber(9916);
I receive:{{"traceId":"6324e22b-cef2-440a-a4ee-f0dc66c5752a","timestamp":"2022-12-07T07:08:09.000" ...
as in the first retryWhen I use
EventPosition eventPosition = EventPosition.FromOffset(98805874928);
I receive:{{"traceId":"6324e22b-cef2-440a-a4ee-f0dc66c5752a","timestamp":"2022-12-07T07:08:09.000" ...
as in the first retryBut when I use
EventPosition eventPosition = EventPosition.FromEnqueuedTime(new DateTimeOffset(DateTime.Parse("2022-12-07T13:08:42.5270000Z")));
I receive:{{"traceId":"21d31271-d42b-4840-961e-8175c50de7b2","timestamp":"2022-12-07T06:45:30.000" ...
as in the second retrySo... Why do two different executions (with the same trigger) return different result?