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
when archive.php is run multiple times, each concurrent run should archive different websites #3405
Labels
Milestone
Comments
(In [7042]) Fixes #3405 Skipping websites which have been processed by another concurrent archive.php |
Will it work if archive.php is launched on different servers but for the "same" database ? |
It should work yes! |
This is a great thing :) |
It's not working in 2.0 |
See follow up #4903 Add possibility to run multiple archiver in parallel |
This was referenced Oct 25, 2013
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
…rchive.php will process websites properly when executed concurrently!
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
Refs matomo-org#3405 fixing regression in concurrent runs
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reported in forums
The goal is to make archiving faster for high traffic piwik server, especially those with thousands of websites. They can exceute php /path/to/cron/archive.php multiple times in parallel, and each instance will archive different websites. Overall it should be much faster than archiving one after the other.
NOte: it used to work as I tested this case when building the feature, but was broken at some point.
The text was updated successfully, but these errors were encountered: