Open migbash opened 5 months ago
π§ UPDATE
Data in the intermediary
sitemaps was corrupted (again), and was caused by the use of the manual regeneration attempt of brand
new fixtures (not picked up by the workflow
).
β Was corrected manually.
Correction of the outlined issue still needs to be corrected as soon as possible.
Is there an existing issue for this?
π Describe the bug
It appears that a case for an error occurs when the
queue
is triggered, in cases where:(column) category
:: fixture is present.(workflow) permalink_queue
process are triggered in succession.π€ Expected Behavior
Should work correctly and on-time.
(optional) π₯οΈ Console Logs (or similar)
^ Has been accumulating
processes
(143 active accululated) for thesitemap-check
process over the last day.(optional) π Additional Information
π First detected on:
25/06/24 at 10:00 CET during testing of links that were sent to the queue.
π Potential initial theorized cause(s)/solution(s):
Cause(s)
Believed (defintive) is that the issue is caused by the:
category
:: fixture, andqueue
workflow triggers sent to thecache-worker
to process forsitemap-check
, which contained thecategory
:: fixture.Potential solution
Throttle
worker
process in cases of which category :: fixture is the process that will be executed. For example: disable thequeue
workflows forsitemap
update when a workflow is already active for the update ofsitemap
for category :: fixture.In ddition, offset the
worker
process for thesitemap
to omit and/or defer the category :: fixture for after the other more important categories(articles_articles, competitions, etc.)
have been processed first.π©Ή Workarounds:
No workarounds found, other than rebooting the
docker container
, to restart process, as it was overwhelemed with jobs and stuck in processing.