sartography/spiff-arena

dev.mod (celery) timers are not working

Opened this issue · 6 comments

madhurrya commented

These timers have not triggered as expected.

Boundary Timer Cycle 1 day
https://dev.mod.spiff.status.im/i/39790

Boundary Timer Cycle 1 hour
https://dev.mod.spiff.status.im/i/39856

Boundary Timer 1 day
https://dev.mod.spiff.status.im/i/39794

Duration Timer 1 day
https://dev.mod.spiff.status.im/i/39796

jakubgs commented

I think it's important to get Celery working, because the old setup generates far too much CPU usage:

image

That's 6 days of app-dev environment, as we can see eventually it reaches pretty much 100% CPU usage.

We can see similar stuff on app-test:

image

But mod-dev with Celery has no such issue:

image

madhurrya commented

@jakubgs we haven't done anything in dev.mod in about a week. The last time I created instances there was on June 10th. Does the graph look similar on that day also?

jakubgs commented

This is the last 16 days on mod-dev:

image

  • 👍1
madhurrya commented

In dev.mod this timer instances are stuck in 'running' state
https://dev.mod.spiff.status.im/process-models/misc:qa:timer-tests:cycle-start-timer-at-mid-night
https://dev.mod.spiff.status.im/i/41491

image

In dev.app it's working as expected
image

jasquat commented

Force running does allow it to complete as usual. I don't know why it's stopping before completing it on its own.

jasquat commented

Ok, so there's an instruction on the EndEvent that is causing it to stop there. The real problem is that we are running this instance from the apscheduler and does not queue the instance back up in celery so it can't continue. Maybe the apscheduler should just queue like everything else.