New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck on Applying queued rearchiving after big installation update to matomo 4 #17474
Comments
Hi @parruc, can you run |
Thanks for the quick response @diosmosis . Sure thing, with that id/date combo I have none but for example:
Some other numbers that may be interesting:
|
A couple more questions @parruc:
|
Sure @diosmosis : To answer tour question our installation has 20030 users, 18 segments (8 pre-processed, 10 processed in real-time) and 19876 websites of which I would say about 70% receive daily traffic (it's a really rough estimate) Plugins (excluded the ones from core and maotmo) are:
|
Hi @parruc, one thing you can do right now is DELETE the How recently did you update to 4.x? If it was relatively recent, you can likely TRUNCATE the archive_invalidations table. This should probably solve the issue for you. |
Hi @diosmosis , Your suggestion worked and now the archive process does not get stuck anymore (I uncommented the incriminated row) so thank you a lot. I still see the archiver memory problem: when it runs for hours the memory consumption skyrockets, but it is probability another thing so I will open another issue if it keeps doing it ;-) Thanks again |
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/matomo-on-premise-scaling/45262/4 |
Expected Behavior
Archive cron does not get stuck on Applying queued rearchiving...
Current Behavior
Archive cron gets stuck during "Applying queued rearchiving..." doing queries like and writing nothing else.
SELECT option_name, option_value FROM
piwik_optionWHERE option_name LIKE '%report_to_invalidate_733_2021-01-29%"
up to a point where it goes out of memory (we have 28GB of memory).
Context
We have a very big matomo installation with more than 20K sites tracked.
We recently updated matomo from 3.12 to 4.2.1
Your Environment
The text was updated successfully, but these errors were encountered: