I know with a scheduler restart, tasks that may still report as running
even though they are not.
On Wed, Aug 9, 2017 at 6:07 PM, David Klosowski
wrote:
> Hi Gerard,
>
> The interesting thing is that we didn't see this issue in 1.7.1.3 but we
> did when upgrading to 1.8.0.
>
> We aren't seeing a
Hi Gerard,
The interesting thing is that we didn't see this issue in 1.7.1.3 but we
did when upgrading to 1.8.0.
We aren't seeing any timeout on the task in question to be quite honest.
The state of the task never changes and we have reasonable timeouts on our
tasks that would notify us. The tas
Hi David,
When tasks are put on the MQ, they are out of the control of the scheduler.
The scheduler puts the state of that task instance in "queued".
What happens next:
1. A worker picks up the task to run and tries to run it.
2. It first executes a couple of checks against the DB prior to execu
