I have django-q set up to run several different background processes -- these processes take anywhere from 10 min to several hours to run.
I want the user to have visibility on which task is currently running, and which tasks are still 'waiting' to be run. Retrieving the queued tasks is straight forward with the ormq object -- but there is no indicator for which of those tasks are currently running.
I thought, that I could just 'assume' that the lowest pk(s) identifiers would always be the ones running - but that does not seem to be the case.
I have django-q set up to run several different background processes -- these processes take anywhere from 10 min to several hours to run.
I want the user to have visibility on which task is currently running, and which tasks are still 'waiting' to be run. Retrieving the queued tasks is straight forward with the ormq object -- but there is no indicator for which of those tasks are currently running.
I thought, that I could just 'assume' that the lowest pk(s) identifiers would always be the ones running - but that does not seem to be the case.
Any thoughts?
@Koed00