Open flauschi opened 5 years ago
Hi @flauschi. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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:
@magento-engcom-team give me 2.3-develop instance
- upcoming 2.3.x release
For more details, please, review the Magento Contributor Assistant documentation.
@flauschi do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Hi @engcom-Charlie. 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).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.3-develop
branchDetails
- Add the comment @magento give me 2.3-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop
branch, please, add the label Reproduced on 2.3.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.
:white_check_mark: Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-19840
were created
Issue Available: @engcom-Charlie, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
Is there an update on the issue?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
This shouldn't be marked as stale.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
Again: This shouldn't be marked as stale.
same issue on magento 2.3.7-p1
Same thing on magento 2.4.2-p2
any news ?
Hi @engcom-Dash. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.same isssue with magento 2.4.6, anyone had fix this? please help...
Hi @flauschi
Thanks for reporting and collaboration.
I verified the issue on Magento 2.4.7 with Elasticsearch 7 but the issue is not reproducible.
Able to see the product on UI after activating the product
Steps to reproduce:
Please take a look at the attached screen recording.
https://github.com/magento/magento2/assets/60198592/ee0edb41-6b6f-4f11-8211-8f25c49c50fb
Hello, the order to trigger this bug is really important: During cron run enable the product after index catalog_category_product has finished updating but before catalogsearch_fulltext index has started processing. In this scenario catalog_category_product is updated in the next cron run. But catalogsearch_fulltext will not run again for this product. This leads to the missing product on the frontend.
This is very theoretically for a small set of products. But for a large set of products and longer running reindex processes this is really a huge problem.
Currently we have worked around this bug by completly avoiding product updates during cron run (by not using the Magento backend for product updates and a asynchronous API to the ERP/PIM systems).
I have found a serious problem with the scheduled reindex of the catalogsearch_fulltext index and the use of Elasticsearch.
Dependencies between the catalogsearch_fulltext index and other indexes (probably catalog_category_product, cataloginventory_stock, catalog_product_price as in Magento/Elasticsearch/etc/indexer.xml) are not taken into account if the mode is set to "UPDATE BY SCHEDULE".
The described steps to reproduce are a very theoretically procedure. But the problem becomes really annoying with imports of many products (and large sets of products waiting for reindex).
The problem could lead to missing products on the frontend. But I think there could be more things.
Could be related to: https://github.com/magento/magento2/issues/13927
Preconditions (*)
Steps to reproduce (*)
The problem is not easy to reproduce, because it is a timing issue:
Expected result (*)
Actual result (*)