Open timothyfisherdev opened 1 month ago
Hi @timothyfisherdev. 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@magento I am working on this
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.
Preconditions and environment
Recently ran a delete query to remove tier pricing for a specific customer group. This removed a lot of rows and is the only thing I can think of that has changed recently.
DELETE FROM catalog_product_entity_tier_price WHERE customer_Group_id = 6
Steps to reproduce
Expected result
Indexers finish
Actual result
catalogrule_product and catalogrule_rule get stuck processing and never finish.
Additional information
When looking into the mysql process list with
show full processlist\G;
, I see two queries that have, at the time of writing, been running for 8+ hours. If I kill either one of them, the process just gets immediately gets replaced with another one running the same query. This is locking up the tables and preventssetup:upgrade
from being ran due to table locks I think.This is the query. "hasmap" is a product attribute that we have, I'm not sure why it's prefixed with `at`.
The only thing that I have done recently is delete tier pricing for a customer group using SQL as mentioned above.
The query above has been running for almost 9 hours now. I've also disconnected all connections to the database temporarily and removed all public web traffic, so Magento is the only thing touching it, which is why I'm pretty sure the query is coming from the indexers.
Release note
No response
Triage and priority