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'd expect it to let long running jobs to execute without setting huge InvisibilityTimeout.
However under some circumstances (alas, can't reproduce intentionally) - like for a week it is fine and than just no - the task is interrupted after 5 minutes (InvisibilityTimeout I guess) with OperationCanceledException and then is tried to requeue (again sometimes there's also a warning about another worker that fetches the task).
Any ideas?
The text was updated successfully, but these errors were encountered:
Looking at the source It has to be something with worker change
stringupdateFetchAtSql=$@" UPDATE ""{_storage.Options.SchemaName}"".""jobqueue"" SET ""fetchedat"" = NOW() WHERE ""id"" = @id AND ""fetchedat"" = @fetchedAt RETURNING ""fetchedat"" AS ""FetchedAt""; ";try{_storage.UseConnection(null, connection =>{FetchedAt=connection.ExecuteScalar<DateTime?>(updateFetchAtSql,new{queue=Queue,id=Id,fetchedAt=FetchedAt});});if(!FetchedAt.HasValue){_logger.Warn($"Background job identifier '{JobId}' was fetched by another worker, will not execute keep alive.");}
so that when fetchedat has changed externally there's.. what? something's wrong?
Why would the worker switch anyway?
Having configuration
I'd expect it to let long running jobs to execute without setting huge InvisibilityTimeout.
However under some circumstances (alas, can't reproduce intentionally) - like for a week it is fine and than just no - the task is interrupted after 5 minutes (InvisibilityTimeout I guess) with OperationCanceledException and then is tried to requeue (again sometimes there's also a warning about another worker that fetches the task).
Any ideas?
The text was updated successfully, but these errors were encountered: