QUALITY PATCH

ACP2E-3705: The indexer_update_all_views cron execution fails when MAGE_INDEXER_THREADS_COUNT is set…

The indexer_update_all_views cron execution fails when MAGE_INDEXER_THREADS_COUNT is set to a value greater than 2, specifically affecting the Customer Segments indexer with B2B enabled. Quality patch ACP2E-3705 for magento/framework applies to Magento Open Source and Adobe Commerce 2.4.7 to 2.4.8-p5.

Categories: Other
Components: magento/framework, magento/module-indexer, magento/module-catalog-permissions
Origin: adobe-commerce-support
Since QPT: 1.1.61

Issue

The indexer_update_all_views cron execution fails when MAGE_INDEXER_THREADS_COUNT is set to a value greater than 2, specifically affecting the Customer Segments indexer with B2B enabled.

Steps to reproduce

1. Apply the QPT patch ACSD-64112. 1. Go to Admin > Stores > Configuration > Catalog > Category permissions. 1. Enable Category Permissions. 1. Set the following indexers to Update on Schedule mode: bin/magento indexer:set-mode schedule catalogpermissions_category catalogpermissions_product 1. Create a few products and assign them to a category. 1. Execute a full reindex. 1. Go to a category and set Category Permissions. 1. Run indexer_update_all_views cron job with MAGE_INDEXER_THREADS_COUNT set to 8.

Adobe's page lists 2.4.7 - 2.4.7-p4 as compatible; the versions below are resolved from the current QPT constraints and are the ones the tool will offer.

Adobe scheduled the permanent fix for 2.4.9.

Install

Install the Quality Patches Tool with composer require magento/quality-patches, apply the prerequisites listed for all files applicable to your distribution and version first, then run vendor/bin/magento-patches apply ACP2E-3705. On Cloud, add ACP2E-3705 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACP2E-3705/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Bundle prerequisites the same way and list them first. Paths are relative to each package root, using the default -p1 level. Prefer local files when configuring composer-patches; a remote URL can change.