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
during core:update display SQL queries as they are executed #7276
Comments
+1 , I almost kill an upgrade a month ago because I wasn't sure it was still running... Hopefully I opend a second SSH session and used "htop" and saw the script running. Going 2.7 to 2.11 for a 14 GB database took 36 minutes (8 GB, 2 CPU MySQL-only server) CPU at 40% while updating. How large is your DB @futureweb ? |
Hi guys, thanks for the suggestion. It's a must-have and we will implement it in the next few months. |
Hey Matthieu, sounds good - thx for picking up my idea so fast! ;-) Andreas |
…(moved CoreUpdater static functions to core/Updater class, remove use of static methods in Updater, don't use static method setUpdater in ColumnsUpdater).
…er in Columns\Updater and document methods in Updater.
…er update process and document UpdateListener.
…notice errors caused by change to Updates.php and add some more functionality to ConsoleCommandTestCase base class.
Hi guys, Can you please stop updating the piwik_log_visits and piwik_log_link_visit_actions These tables are huge on any normal high traffic site. It would be much better to create a new table and do a 1:1 mapping. The cost on inserting into multiple tables cannot justify being down for 8 hours while the update is completing which is what is happening in our case now. |
@samgabriel currently such DB schema changes are blocked, see issue #6953 |
Btw I think it already works to do |
That doesn't tell you the progress, and it shows every SQL statement Piwik uses, including statements that are irrelevant to the update. Nor is the output particularly easy to read. |
Fixes #7276 display update progress in core:archive command. Includes Updater refactor: deprecate static methods in Updates in favor of instance methods that are passed an Updater instance, use instance methods in Updater, move methods in CoreUpdater that perform updates to Updater class, add observer class that can be used within Updater to hook into single updater run.
Hi,
we got a pretty large Piwik DB - and DB Updates on Piwik Updates often takes several hours to complete ... It would be VERY HELPFUL if the CLI Update Script (console core:update) would show some information on progress ...
I know it's not possible to output estimated time left ... but you could output something like
"14 out of 147 Queries finished"
"15 out of 147 Queries finished"
"16 out of 147 Queries finished"
Would be a good feeling to see there is some progress while waiting a few Hours for the Script to complete ... ;-)
Thank you, bye from Austria
Andreas Schnederle-Wagner
The text was updated successfully, but these errors were encountered: