You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of Azure.Messaging.EventHubs v5.11.0, the format of checkpoints written to blob storage has changed. Notably, the value of offset is null. In our case, this caused KEDA to over-scale a service. Downgrading the SDK to v5.10.0 resolved the issue.
In response to my original issue, it was asserted by a Microsoft contributor that this change is intentional and that the implementation of checkpoints are not to be relied upon.
Please refer to the original issue for more in-depth details and reproduction steps.
Expected Behavior
I expected KEDA to scale my service appropriately.
Actual Behavior
KEDA over-scaled the service until the Azure SDK was downgraded and the old checkpoint format restored.
Steps to Reproduce the Problem
privateasyncTaskProcessEventAsync(ProcessEventArgseventArgs){awaiteventArgs.UpdateCheckpointAsync();// breakpoint here and examine Offset in memorylog.LogInformation("checkpoint created");// breakpoint here and examine offset in checkpoint}