-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Product bulk update is not working.even cron job is running as per magento standard. #27002
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @santosh-ks153. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
For more details, please, review the Magento Contributor Assistant documentation. @santosh-ks153 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
Could you try to disable Magento_Amqp and Magento_AmqpStore modules and after that add a new bulk job to the queue? There are some reports that disabling these modules would solve the hanging jobs. |
okay let me try this. |
Magento_AmqpStore is not available in Magento 2.3.2. |
also, I did this step with no luck. Is it core bugs? |
Our site kept getting stuck cron jobs and high ram usage due to stuck processes, this appears to have been solved by adding the code below to env.php:
This does presume you are not using RabbitMQ though. |
I did this step as well but still no luck.
…On Tue, Feb 25, 2020, 4:14 PM devchris79 ***@***.***> wrote:
Our site kept getting stuck cron jobs and high ram usage due to stuck
processes, this appears to have been solved by adding the code below to
env.php:
,
'cron_consumers_runner' => [
'cron_run' => false,
'max_messages' => 1000,
'consumers' => [
'async.operations.all'
]
]
This does presume you are not using RabbitMQ though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27002?email_source=notifications&email_token=ANJ7CFDWDZVOSNPEKOUU6WDRETZBLA5CNFSM4K3CQZVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM3PGOY#issuecomment-590803771>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANJ7CFBQPUROHCTV6NLMRCLRETZBLANCNFSM4K3CQZVA>
.
|
It may also be worth checking you ram usage |
I don`t think its ram usage issue but let me try with that. |
I don't think it is a general bug, because bulk updates are working here. However, we are on 2.3.3 |
yes, that why I m asking it core bugs with 2.3.2? |
It should also be working on Magento 2.3.2, I've tested this quite extensively. @santosh-ks153: you'll probably need to do a bit of debugging, maybe this helps: #23450 (comment) |
I did every possible solution available on Google with no luck. |
@santosh-ks153 run: php bin/magento queue:consumers:start product_action_attribute.update |
Hi @santosh-ks153 , I am closing this issue. Feel free to reopen still you are facing issue. Thanks |
Truncating cron_schedule table manually fixed the issue for me. |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
I want to update the product.
Actual result (*)
The text was updated successfully, but these errors were encountered: