Hi @jedie,
I had a bad surprise this morning while checking on the progress of a process which had it's first sub-process running for over than 24h.
There was an error: django.db.utils.OperationalError: (1114, "The table 'huey_monitor_taskprogressmodel' is full")
Then I realized that for each tiny progress report, a record is created for TaskProgressModel
Could you please tell me what is the benefit of creating a new TaskProgressModel (even two when you want to report progress on both sub-task and maintask) each time you report a progress vs. incrementing directly the progress_count field of an existing TaskProgressModel ?
That would mean that in general, we would have only one TaskProgressModel for each TaskModel.
Thanks in advance for your feedback
Hi @jedie,
I had a bad surprise this morning while checking on the progress of a process which had it's first sub-process running for over than 24h.
There was an error:
django.db.utils.OperationalError: (1114, "The table 'huey_monitor_taskprogressmodel' is full")Then I realized that for each tiny progress report, a record is created for
TaskProgressModelCould you please tell me what is the benefit of creating a new
TaskProgressModel(even two when you want to report progress on both sub-task and maintask) each time you report a progress vs. incrementing directly theprogress_countfield of an existingTaskProgressModel?That would mean that in general, we would have only one
TaskProgressModelfor eachTaskModel.Thanks in advance for your feedback