3

If Magento Enterprise's indexers have crashed or your database has crashed or was dumped during a re-index, you might get stuck with an indexer lock. This lock can only be removed by the MySQL thread which has started it.

So how to do this?

5

The solution to such a situation is to log into mysql and:

mysql> SHOW PROCESSLIST;
+------+------------+-----------+----------+---------+----------+-------+------------------+
| Id   | User       | Host      | db       | Command |     Time | State | Info             |
+------+------------+-----------+----------+---------+----------+-------+------------------+
| 4185 | mysql_user | localhost | mysql_db | Query   |        0 | NULL  | show processlist |
| 4384 | mysql_user | localhost | mysql_db | Query   |    23489 | NULL  |                  |
+------+------------+-----------+----------+---------+----------+-------+------------------+
2 rows in set (0.00 sec)
mysql> KILL 4384;
3

Go to var/locks and check for full_reindex.lock file remove that.

  • The question is about a MySQL lock, not a file lock. – Robbie Averill Jun 14 '16 at 22:03
  • This message "Full reindex process is already running" could also happen when this full_reindex.lock file exists. This is a correct answer. – Ryan Street Feb 28 '18 at 23:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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