-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[Bug] Regression: Matomo ignores --concurrent-archivers=3 option on core:archive #21985
Comments
The user had a second Matomo instance, on Matomo 4. But now they report this: We've had the same behavior on the 2nd instance since the matomo 5 update on Friday night. |
As already mentioned internally we need more details to reproduce the issue. Just using Without more knowledge of the system it may be impossible to reproduce (and fix) it. |
I sent a message to the person who discovered this issue. |
The user found a workaround as follows:
|
Closing as duplicate of #22508, as the other issue contains more detailed information about the actual problem. |
What happened?
You can run 4 or more crontabs of the following command, simultaneously, in parallel, Matomo doesn't try to stop you:
core:archive --no-ansi --no-interaction --concurrent-archivers=3 --concurrent-requests-per-website=4 --max-archives-to-process=200 --disable-scheduled-tasks --force-idsites=11
What should happen?
When attempting to start too many archivers, here is the expected message:
How can this be reproduced?
For core:archive:
Here is the syntax used by the person who reported this problem:
core:archive --no-ansi --no-interaction --concurrent-archivers=3 --concurrent-requests-per-website=4 --max-archives-to-process=200 --disable-scheduled-tasks --force-idsites=11
Notice the log output below. You can see that four archivers start up, each reporting that 0 of 3 are running.
(In the private Jira version of this ticket I have included more information. The user says that before upgrading to Matomo 5, this bug did not occur in Matomo 4)
Matomo version
5.0.1
Server operating system
Linux
Relevant log output
Validations
The text was updated successfully, but these errors were encountered: