Price indexer running for multiple hours with 2.1 million products

[ioweb-gr]

Preconditions and environment

• 2.4.5-p2

Steps to reproduce

We have created a website with 45974 configurable products and a total of 2.1 million products with their variations + simple products

Reindexing process crashed in scheduled mode and for some reasons and we need to reindex them fully.

Unexpectedly though the reindex process runs for too many hours for the price indexer and this leads to products not displaying in the frontend as in order to reindex the catalog search index and the category products index, the price index must run as well but it takes too long.

Now our frontend is missing products

Is magento even able to handle the 2.1m products? What can I do to make it run faster? Changing the batch size has no effect whatsoever, the speed is horribly slow.

Expected result

All indexers run fast.

Actual result

Reindexing is slow.

Additional information

No response

Release note

No response

Triage and priority

• [x] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @ioweb-gr. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[hostep]

Not sure if it is the same issue, but there is a bug in Magento 2.4.x (not in 2.3.x) with the indexers where the partial indexer could loop unnecessarily many times over the same entities to index and sometimes even skip indexing entities it should reindex. That was fixed in https://github.com/magento/magento2/pull/36155 (which is supposed to be included in Magento 2.4.7)

[amouri82]

Hello, @hostep there is a patch to fix this issue or not yet ? We are facing the same problem and can't wait next release to fix it. Thanks

[hostep]

@amouri82: Start from the diff of the PR: https://patch-diff.githubusercontent.com/raw/magento/magento2/pull/36155.diff And see if you can apply that as a patch (you'll have to convert the paths so you can apply it to a composer installation).

We do have a patch of our own, but it was based on an older version of the PR (some extra changes made it in after we created our patch). So I'm not sure if I should share it here as it is a bit outdated.

[amouri82]

@hostep Thanks you for your replay and the diff of the PR. I will try to create owr own patch and share it if works. Thanks.

[engcom-Dash]

Hi @ioweb-gr

Thanks for reporting and collaboration.

As per the above comments the issue is fixed in https://github.com/magento/magento2/pull/36155 in Magento 2.4.7

Please try to reproduce the issue in magneto 2.4.7 and let us know if you still face the issue.

Thanks

[m2-assistant[bot]]

Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.