You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to improve archiving performance, we have 10 cron archive tasks in our on premise Matomo installation.
It has been that way for long time with no problem at all: the cron tasks distributed the sites and all of them were archived only once.
However, we had to hook the CronArchive.archiveSingleSite.start event and, since that moment, we observe that the code in CronArchive.archiveSingleSite.start is being executed concurrently by several crons tasks.
Is there any way to avoid that concurrency?
Is there any other place, event or technique to, for each site, execute a piece of code before proceding with the archive but making sure its execution mutually excluded for the site?
The text was updated successfully, but these errors were encountered:
In order to improve archiving performance, we have 10 cron archive tasks in our on premise Matomo installation.
It has been that way for long time with no problem at all: the cron tasks distributed the sites and all of them were archived only once.
However, we had to hook the
CronArchive.archiveSingleSite.start
event and, since that moment, we observe that the code inCronArchive.archiveSingleSite.start
is being executed concurrently by several crons tasks.Is there any way to avoid that concurrency?
Is there any other place, event or technique to, for each site, execute a piece of code before proceding with the archive but making sure its execution mutually excluded for the site?
The text was updated successfully, but these errors were encountered: