General error: 1205 Lock wait timeout exceeded; try restarting transaction error on Magento 2.1.2

General error: 1205 Lock wait timeout exceeded; try restarting transaction error on Magento 2.1.2

July 12, 2026 · Illustrated author avatarBy Stefan Bogdanescu
General error: 1205 Lock wait timeout exceeded; try restarting transaction error on Magento 2.1.2

Solving “Lock Wait Timeout Exceeded” Error in Magento 2.1.2

If you’re encountering the “Lock wait timeout exceeded; try restarting transaction” error while adding new products in Magento 2.1.2, don’t worry—you’re not alone. This common issue can be frustrating for developers and store owners alike, but it’s solvable with the right approach.

Understanding the Error

The error message “Lock wait timeout exceeded; try restarting transaction” typically occurs when two or more processes are attempting to access the same database record simultaneously. In other words, a lock is placed on the record by one process while another process is waiting for that lock to be released, causing a timeout.

In Magento 2.1.2, this usually happens during product creation due to the way attribute updates are handled, especially if you’re working with a large number of attributes or have high concurrent traffic.

Why Changing innodb_lock_wait_timeout Doesn’t Always Work

As mentioned in your question, changing the innodb_lock_wait_timeout value in the MySQL configuration file is one potential solution. This setting determines how long the server waits for an unlock before giving up and returning a timeout error.

However, simply increasing this value doesn’t always solve the problem. The issue often persists because the underlying cause isn’t addressed—too many concurrent processes still compete for the same locks simultaneously.

Effective Solutions to Resolve the Error

1. Optimize Your Database Schema and Indexes

Ensure your database schema is optimized, especially for tables that handle product data. Review your indexes and make sure they are appropriate for your queries. Over-indexing can slow down write operations, while under-indexing can cause excessive locking.

2. Limit Concurrent Operations During Product Save/Update

Use Magento’s built-in features to control concurrent operations during product save or update processes. You can achieve this by implementing a lock mechanism at the application level before starting any long-running transactions involving multiple products.

Here’s an example of how you might implement a lock using a static variable in your custom module:

class MyModule\Observer\SaveProductBefore
{
    private static $lock = false;

    public function execute(\Magento\Framework\Event\Observer $observer)
    {
        if (!self::$lock) {
            self::$lock = true;
            // Your product saving logic here
            self::$lock = false;
        }
    }
}

This example uses a simple lock mechanism to ensure only one instance of the observer can run at a time. However, this is just a basic demonstration; real-world applications would require more robust locking mechanisms.

3. Upgrade Magento to a Later Version

Magento has addressed several performance and concurrency issues in later versions. If possible, upgrade your Magento installation to a newer version (e.g., 2.4.x) that includes these improvements.

Conclusion: A Comprehensive Approach to Resolving Lock Timouts

The “lock wait timeout exceeded” error is a complex issue that often requires more than just adjusting MySQL configuration settings. By combining database optimization, application-level locking mechanisms, and keeping your Magento version up-to-date, you can effectively resolve this problem in most cases.

Remember, the key is to identify the specific cause of the lock contention—it could be due to heavy traffic, long-running transactions, or inefficient queries—and address it accordingly with a multi-pronged approach.

Magento 2 Catalog Database API

Our network