Magento - Catalog URL Rewrites -> Processing

Magento - Catalog URL Rewrites -> Processing

September 11, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento - Catalog URL Rewrites -> Processing

Resolving Magento Catalog URL Rewrites Indexing Issue

The Problem: Stuck on PROCESSING

You’re facing an indexing issue where your catalog URL rewrites are stuck in the PROCESSING state, even after you’ve tried various troubleshooting steps like truncating the core_url_rewrite table and deleting lock files. When attempting to reindex via SSH or the backend, it seems to be trapped in a loop with no progress.

Understanding the Indexing Process

In Magento, the catalog URL rewrites index is responsible for generating clean, search engine-friendly URLs for your products. The indexing process involves several steps:

  1. Truncation: Magento first truncates (empties) the core_url_rewrite table.
  2. Processing: It then starts processing the data to generate new URLs based on product and category configurations.
  3. Insertion: Finally, it inserts the generated URLs back into the core_url_rewrite table.

Why Your Indexing is Stuck

The issue might be due to a few common reasons:

1. Resource Overload

If your server resources (CPU, memory) are maxed out, Magento won’t be able to complete the indexing process efficiently. Check your system’s resource usage during reindexing.

2. Database Configuration

Your database configuration may not be optimized for handling large datasets or concurrent connections. Ensure your MySQL settings are properly tuned.

3. Corrupt Index Data

Sometimes, the data in the core_url_rewrite table can become corrupt, causing Magento to get stuck during processing.

How to Resolve the Issue

1. Optimize Your Server and Database

Before proceeding with any technical solutions, make sure your server is well-configured for running a Magento store:

  • Ensure you have adequate memory allocated.
  • Configure your MySQL settings appropriately (e.g., increase innodb_buffer_pool_size).
  • Use a reliable hosting provider that supports Magento’s resource requirements.

2. Reindex Manually via SSH

To manually reindex the catalog URL rewrites, use the following command in your terminal:

php bin/magento indexer:reindex catalog_url --mode=update-by-schedule

Note:

  • Replace catalog_url with any other relevant index if required.
  • The --mode=update-by-schedule flag ensures Magento updates the index as per its scheduled process.

3. Check for Corrupt Data

If the manual reindexing step fails, check your database for any anomalies:

  1. MySQL Health Check: Use tools like MySQL Health Monitor to scan your MySQL server.

  2. Database Table Check: Run a CHECK TABLE command on the core_url_rewrite table:

CHECK TABLE core_url_rewrite;

If any errors are reported, perform a repair using REPAIR TABLE core_url_rewrite;.

4. Reinstall Your Indexer

If all else fails, you can reinstall your indexer using the following commands:

  1. Truncate the table: Empty the core_url_rewrite table.
TRUNCATE TABLE core_url_rewrite;
  1. Reindex via SSH: Run the same reindex command as mentioned earlier.

  2. Clear cache and refresh indexes:

    • php bin/magento cache:clean
    • php bin/magento indexer:status (to check status)
    • php bin/magento indexer:reindex

Conclusion

Resolving Magento indexing issues requires a systematic approach involving resource optimization, database checks, and manual intervention. Always remember to backup your data before performing any database operations.

For more detailed guides on Magento performance tuning and troubleshooting, visit our Magento Performance Optimization Guide at Laravel Company.

Catalog Indexing Database Performance

Our network