Title: Elementor Data Updater + High CPU Usage Issues
Last modified: September 10, 2019

---

# Elementor Data Updater + High CPU Usage Issues

 *  [jacksmithy](https://wordpress.org/support/users/jacksmithy/)
 * (@jacksmithy)
 * [6 years, 9 months ago](https://wordpress.org/support/topic/elementor-data-updater-high-cpu-usage-issues/)
 * Issue with version 2.7.1
 * Hi,
 * The notification below wouldn’t disappear despite clicking on “Click here to 
   run it now” button many times (over 20 times). Also the server CPU has gone from
   1% to nearly 90% causing everything else to run very slow and about to crash.
 * I uninstalled and re-installed the plugin and I am still getting the same notification
   below:
 * ——-
    Elementor Data Updater – Database update process is running in the background.
 * Taking a while? Click here to run it now
    ———-
 * Could you please fix this as the previous version didn’t have this issue.
 * I had to remove it completely until a fix issued.
 * PS: I having been using WPBakery for many years with no issues. I only started
   using yours for the last day or so and I had to contact you..
 * Please double check your updates before releasing new updates to the public.
 * Kind regards
    Jack

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [kingneb](https://wordpress.org/support/users/kingneb/)
 * (@kingneb)
 * [6 years, 9 months ago](https://wordpress.org/support/topic/elementor-data-updater-high-cpu-usage-issues/#post-11927125)
 * Jack,
 * I had the same problem. I disabled my cache plugins, clicked the button, and 
   it worked.
 * Try disabling some plugins, esp. cache plugins, and click to update. Then reactivate
   your plugins.
    -  This reply was modified 6 years, 9 months ago by [kingneb](https://wordpress.org/support/users/kingneb/).
 *  Thread Starter [jacksmithy](https://wordpress.org/support/users/jacksmithy/)
 * (@jacksmithy)
 * [6 years, 9 months ago](https://wordpress.org/support/topic/elementor-data-updater-high-cpu-usage-issues/#post-11930341)
 * Thanks [@kingneb](https://wordpress.org/support/users/kingneb/)
 * Very disappointing that the guys from Elementor are not interested in supporting
   the free users of their buggy plugin! Even though this bug is caused by them.
 * Disabling and enabling the plugin didn’t work for me.
 * Here’s what I did to get it working, just in case someone has the same issue 
   and the Elementor staff won’t help:
 * 1- Delete the Elementor plugin (your settings should be save – you are only deleting
   the files from your server – not from your database – you can backup your database
   to be on the safe side)
 * 2- Disable all plugins (enable maintenance mode if you have a plugin for that–
   no one likes a messy site)
 * 3- Re-install Elementor
 * 4- Rolled back Elementor to version 2.7.0 (go to Elementor >>Tools >> Version
   Control >>> select 2.7.0 and hit Reinstall v2.7.0).
 * 5- You will see update notification for Elementor v2.7.1- click update.
 * 6- You will see this notice: Elementor Data Updater – Database update process
   is running in the background. Taking a while? Click here to run it now
 * 7- Click run it now and it should work 😉
 * 8- Enable your plugins and monitor your server to be on the safe side!
 * Done!
 * I hope that helps and thanks again [@kingneb](https://wordpress.org/support/users/kingneb/)
   for your help!
 *  Thread Starter [jacksmithy](https://wordpress.org/support/users/jacksmithy/)
 * (@jacksmithy)
 * [6 years, 9 months ago](https://wordpress.org/support/topic/elementor-data-updater-high-cpu-usage-issues/#post-11935925)
 * Quick update:
 * Elementor has just released a new update to fix the [updater stuck and high CPU]
   issue in today’s 2.7.2 update. Let’s hope this update won’t fire any CPUs or 
   cause any further issues!
 * Elementor, Why did you release an update with major bug without back-end testing?
 * Testing……
 * ——————
 * 2.7.2 – 2019-09-16
 *  Fix: Data updater stuck in site with large database ([Topic](https://wordpress.org/support/topic/the-elementor-data-updater-problems-continue/),
   [Topic](https://wordpress.org/support/topic/v2-7-not-stable/))
    Fix: Added backward
   compatibility for deprecated hooks in page settings (#9060, #9080) Fix: Added
   support for custom document in autosave (#9070) Fix: Changed the default slidesPerGroup
   from 2 to 1 in Image Carousel widget
    -  This reply was modified 6 years, 9 months ago by [jacksmithy](https://wordpress.org/support/users/jacksmithy/).
 *  Thread Starter [jacksmithy](https://wordpress.org/support/users/jacksmithy/)
 * (@jacksmithy)
 * [6 years, 9 months ago](https://wordpress.org/support/topic/elementor-data-updater-high-cpu-usage-issues/#post-11935986)
 * Don’t update to v2.7.2 it is even worst than v2.7.1
 * It will bring the whole site down this time not just high CPU usage and stuck
   updater.
 * Well done Elementor!
 * Further details about the errors in [this topic ](https://wordpress.org/support/topic/2-7-2-errors/#post-11935971)
    -  This reply was modified 6 years, 9 months ago by [jacksmithy](https://wordpress.org/support/users/jacksmithy/).

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Elementor Data Updater + High CPU Usage Issues’ is closed to new replies.

 * ![](https://ps.w.org/elementor/assets/icon-256x256.gif?rev=3444228)
 * [Elementor Website Builder - more than just a page builder](https://wordpress.org/plugins/elementor/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/elementor/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/elementor/)
 * [Active Topics](https://wordpress.org/support/plugin/elementor/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/elementor/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/elementor/reviews/)

## Tags

 * [high cpu usage](https://wordpress.org/support/topic-tag/high-cpu-usage/)

 * 4 replies
 * 0 participants
 * Last reply from: [jacksmithy](https://wordpress.org/support/users/jacksmithy/)
 * Last activity: [6 years, 9 months ago](https://wordpress.org/support/topic/elementor-data-updater-high-cpu-usage-issues/#post-11935986)
 * Status: not resolved