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
I have a situation where one particular job which is ran every 5 minutes. It takes around 3 minutes to finish. And sometimes it behaves strangely:
It does not finish (based on lack of corresponding message in logs)
Job trigger remains in BLOCKED state, so it never runs again.
Logs show no errors whatsoever, so it is hard to reason what could go wrong. Also, it happens very randomly, around once a day. Hard to catch and debug.
The app is .NET 6 hosted service running under AWS ECS cluster, single node. Job has DisallowConcurrentExecution attribute.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a situation where one particular job which is ran every 5 minutes. It takes around 3 minutes to finish. And sometimes it behaves strangely:
BLOCKED
state, so it never runs again.Logs show no errors whatsoever, so it is hard to reason what could go wrong. Also, it happens very randomly, around once a day. Hard to catch and debug.
The app is .NET 6 hosted service running under AWS ECS cluster, single node. Job has
DisallowConcurrentExecution
attribute.Any suggestions on debugging strategy?
Beta Was this translation helpful? Give feedback.
All reactions