-
Notifications
You must be signed in to change notification settings - Fork 2.3k
A lot of error logs "TaskId: <ID> could not be found while executing HTTP" #3022
Comments
hI @astelmashenko , Which type of executionDAO are you using? Looks like it is in an unstable state. Can you clean up and restart the conductor again? |
@astelmashenko this error is printed because a HTTP task was posted to the queue with its task id. But when the executor of that HTTP task polled and started executing it, the task is not found in the persistence store. This could be a race condition. For production use-cases, it is necessary to have a lock implementation. Please consider using one. |
Thanks guys, I've looked through source code and found out it was due to absence of a lock service. We are in process of adding lock service. I'm closing this issue. |
This happened again, this time we have a lock enabled. Most likely after conductor upgrade, restart happened such errors appeared in logs. |
@manan164 , is it possible that during restart lock service is stopped in incorrect order, is there something like graceful shutdown and critical services are started first and stopped last? |
This issue is stale, because it has been open for 45 days with no activity. Remove the stale label or comment, or this will be closed in 7 days. |
This issue was closed, because it has been stalled for 7 days with no activity. |
Describe the bug
Just seeing a lot of errors. Conductor works.
Details Updated
Conductor version: 3.13.6
Persistence implementation: Postgres
Lock: Redis
The text was updated successfully, but these errors were encountered: