Thanks in advance for reading, and for any help you can hopefully offer.

My company uses Magento for our marketplace, and while we've always had occasional issues with AOE Scheduler unable to kick off an enterprise_refresh_index, lately it's been happening far more often, and at a rate that's actually hampering our Merchandising team's ability to operate, due to the rogue enterprise_refresh_index seeming to hold table locks that are causing INSERT/DELETE/UPDATE timeouts on VERY simple Merchandising operations.

It's crippling their ability to merchandise & update products & categories throughout the day, so it's crucial we track down what's causing this rogue enterprise_refresh_index that's not being handled by AOE Scheduler.

Useful info about our setup:

  • Magento ver.
  • MySQL 5.6.34

Extensions of note:

  • AOE Scheduler (1.5.0)
  • LogicBroker (1.0.8)
  • Amasty (Mass Product Actions 1.5.8, Extended Product Grid with Editor 4.12.4, Shipping Table Rates 2.2.3, Image-Based Dynamic Configurable Products 3.11.7)
  • Klevu (Replaces Mage search entirely, 1.2.5)

enterprise_refresh_index cron setup enterprise_refresh_index cron setup*

index management configured in backend index management configured in backend

enterprise_refresh_index erorr details from our investigations:

  • An enterprise_refresh_index is being kicked off by something we can't trace
  • We notice the issue via the usual error AOE Scheduler throws when it's having indexing issues:

    Cron error while executing enterprise_refresh_index:

    exception 'Enterprise_Index_Exception' with message 'Can't lock indexer process.' in /APP/magento/app/code/core/Enterprise/Index/Model/Observer.php:140 Stack trace:

    [internal function]: Enterprise_Index_Model_Observer->refreshIndex(Object(Aoe_Scheduler_Model_Schedule))

  • This isn't an AOE Scheduler-triggered run, as it's throwing ERRORs in the Job List trying to execute.

    • AOE Scheduler errors out until the running re-index finishes
    • This rogue index usually takes 5 to 20 minutes to complete
    • We've had it go for as long as 4 hours recently, with little pauses in-between of errors
  • We can see the active re-index going on when viewing Client Connections to the Marketplace DB; the queries to run a enterprise_refresh_index are chugging away, without any insight into what triggered this run.

    Here's a look at our MySQL connections when it is happening. Note that there's not subsequent sleeping magentouser threads that could be blocking the index or anything. Just the rogue re-index running wild.

    MySQL Connections

  • This rogue indexer often blocks our merchandising team’s updates to products & categories

    • They get lock timeouts updating products at an extreme rate during this window, and the updates are usually small / should be easy to execute, aside from the indexer causing issues
    • The merchandising lock timeout errors don't seem to happen when the rogue index isn't running; We’ve gone through every failed save in the admin access log, EVERY one of them, and all of them correlated to a time when AOE Scheduler was throwing ERRORs when trying to run the enterprise_refresh_index. Even the most basic of product / category updates can be blocked by this re-index.

    • Locks happen for our merch team most frequently when trying to DELETE/INSERT into catalog_product_entity_int / catalog_category_entity / catalog_category_product

    • The locks even happen to simple row-level operations, which seems to imply the indexer is taking table locks (but we can’t locate or pinpoint the lock / where the lock is held & managed from?):

      error: SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction, query was: DELETE FROM catalog_product_entity_int WHERE (attribute_id = '306') AND (entity_id = '205532') AND (store_id <> 0)

      error: SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction, query was: UPDATE catalog_category_entity SET entity_type_id = ?, attribute_set_id = ?, parent_id = ?, created_at = '2017-12-26 20:47:53', updated_at = '2018-01-26 21:49:18', path = ?, position = ?, level = ?, children_count = ? WHERE (entity_id=642)

    • Running DB statistics queries during these rogue indexers do NOT show any db or table locks in use, or active locked mysql indexes on these tables.

We're at the point where we assume one of two things, after exhausting all debugging options we can think of:

  • A 3rd party module we don’t expect to be doing so is kicking off an enterprise_refresh_index or triggering an observer with some updates it performs
  • Related to theory 1: Magento has a default observer, that despite manual reindexing & AOE Scheduler handling enterprise_refresh_index, is naturally kicked off by some setup of our cron jobs or some action taken by a 3rd party module triggering an observer.
    • We're hoping it's not this, as that's far harder to track down in theory…

Worthwhile bonus data:

  • The memory usage of the failed / errored enterprise_refresh_index jobs in AOE Scheduler's list is always 11.06 MB.
  • Every failed Merchandising "Save" correlates to these enterprise_refresh_index errors, but they are able to occasionally sneak product updates in while these errors occur

We're hoping for any avenues or ideas from people who may have had similar experiences, and not managed to document the solution online, or maybe trigger a solution from shop(s) experiencing similar issue(s).

We know this issue has been discussed a lot, but no one has ever had this set of scenarios where an unknown enterprise_refresh_index is holding tables hostage for so long that simple merchandising updates are failing. Our merch team has been super patient, but the more we grow as a company, the more our catalog grows, the bigger the problem becomes... Any help is appreciated.

Let me know if providing more info will help you with your theories / ideas. Thanks all.

Edit: Still looking for any help. Cheers!


1 Answer 1


The issue came from Rapidflow. Our index settings for import for RapidFlow jobs was set to AUTOMATIC (Immediately after import). Setting it to MANUAL let AOEScheduler pick up the changes via the scheduled enterprise_refresh_index, and stopped locking AOEScheduler out of the indexer. All set.

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.