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?

Improve this question

2 Answers 2

Reset to default
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;
Improve this answer
0
3

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

Improve this answer
2
  • The question is about a MySQL lock, not a file lock. Commented Jun 14, 2016 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. Commented Feb 28, 2018 at 23:07