DocumentationCommerceTools

[PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."}

ACSD-67091: Catalog rule product index cleanup fails due to maximum writeset size during large deletions

Last update: Mon Mar 09 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
  • Developer

The ACSD-67091 patch fixes the issue where the catalog rule product index cleanup fails due to maximum writeset size during large deletions. This patch is available when the Quality Patches Tool (QPT) 1.1.76 is installed. The patch ID is ACSD-67091. Please note that this issue is scheduled to be fixed in Adobe Commerce 2.4.9.

Affected products and versions

The patch is created for Adobe Commerce version:

  • Adobe Commerce (all deployment methods) 2.4.8

Compatible with Adobe Commerce versions:

  • Adobe Commerce (all deployment methods) 2.4.8 - 2.4.8-p3
NOTE
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches package to the latest version and check the compatibility on the Quality Patches Tool: Search for patches page. Use the patch ID as a search keyword to locate the patch.

Issue

Catalog rule product index cleanup fails with a maximum writeset size error during large deletions.

Prerequisites:

Your instance must have multiple websites, more than 100,000 products, several customer groups, and more than 20 catalog price rules.

Steps to reproduce:

  1. Run reindexing to generate data and populate the catalogrule_product table using the following command:

    code language-none 
    bin/magento indexer:reindex catalogrule_product

  2. Make multiple catalog changes, and then run reindexing again.

  3. Observe that the catalogrule_product table is cleared using a single delete operation.

Expected results:

  1. Large catalogrule_product tables are cleared without issues.
  2. The indexer deletes data in manageable batches to avoid transaction limits.
  3. No critical performance degradation or failures occur during standard index operations.

Actual results:

  1. The catalogrule_product table is cleared using a single large delete query that affects more than 50 million records.
  2. MySQL returns the error: WSREP: transaction size limit (2147483647) exceeded.
  3. The indexer operation fails due to writeset size limitations.
  4. Database performance degrades because millions of rows are deleted in a single transaction.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

To learn more about Quality Patches Tool, refer to:

recommendation-more-help
c2d96e17-5179-455c-ad3a-e1697bb4e8c3