Azure
Timer Trigger intermittently triggering multiple AKS container instances at the same time
We got a timer-based trigger built on Dotnet core 3.1 and deployed to multiple regions in AKS cluster.
- It triggers every 30 seconds.
- Two instances were deployed in each region.
- All are using the same storage account.
We recently noticed that two instances in the same region intermittently trigger simultaneously, as shown in the screenshot below, even though the timer trigger always ensures one instance per Microsoft documents.
We call a stored proc under the hood. So triggering of multiple instances is leading to issues with data integrity The easiest solution is to scale down to one instance. Is there any option to fix it more properly?
@krishnad1982 Please provide us the function app name so that we can check further.
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.
