Price indexers make queries flood MariaDb until the site drops (Please reopen #36667)

[ioweb-gr]

Today I faced this issue again and caught it really early and briefly I noticed that the holdup came when the indexer was renaming price tables to _outdated or something like this I'm assuming to move the replica table into it's place.

During these rename queries, the other queries started piling up and the system dropped.

On my system the price tables are fairly large now.

So renaming a table like this would most likely take considerable time.

This is a followup on #36667

[m2-assistant]

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.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 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.

[ioweb-gr]

Normally rename shouldn't take that long to execute unless the table is locked. I think there are multiple locks placed on the tables during price indexing which cause deadlock and that's why rename gets stuck there. When the rename got finished, all other queries finished fast.
Is it possible the table is locked both by the rename process and the scheduled indexers processing prices at the same time causing the deadlock?

We're really buffled as to what is causing these random downtimes due to this and eliminated all other factors we could

[m2-assistant]

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: 👇

• 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.

[engcom-Dash]

Hi @ioweb-gr ,

Kindly Provide Additional Information About this issue...It's very easy to proceed further.So Kindly Update below information
1.Steps to reproduce
2.Precondition
3.Actual result
4.Expected Result.

Thanks.

[ioweb-gr]

@engcom-Dash The problem is I can't find the proper steps to reproduce. Could you please provide any input as where those queries could be coming from so we can add some logs perhaps that can help us find the steps to replicate?

[engcom-Dash]

Hi @ioweb-gr ,

With all due respect, it seems to be a duplicate issue of ticket number 36667 Hence We are closing this ticket and we will follow the parent issue (#36667).

Thanks.