Skip to content
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

WebAPI products are not removed from Elasticsearch #30282

Open
magento-engcom-team opened this issue Oct 1, 2020 · 5 comments
Open

WebAPI products are not removed from Elasticsearch #30282

magento-engcom-team opened this issue Oct 1, 2020 · 5 comments
Labels
Area: APIs CD Issue recommended for the contribution day Component: Other Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: ready for dev Reported on 2.4.0 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.

Comments

@magento-engcom-team
Copy link
Contributor

In WebAPI testing, I saw that products were being added to elasticsearch but never removed. I'm unsure if this is normal. Many products are being deleted but some are not. This causing a slow increase in Elasticsearch memory usage. I specifically looked at GraphQL.

<2020-07-06T18:09:13,718][INFO ][o.e.c.m.MetaDataCreateIndexService] [139ed5ecd08c] [magento2*product_8*v2] creating index, cause [api], templates [], shards [1]/[1], mappings []

[2020-07-06T18:09:13,809][INFO ][o.e.c.m.MetaDataMappingService] [139ed5ecd08c] [magento2*product_8_v2/IwEuwlSSQCCfAf7K5Qq-RA] create*mapping [document]

[2020-07-06T18:09:14,220][INFO ][o.e.c.m.MetaDataDeleteIndexService] [139ed5ecd08c] [magento2*product_8*v2/IwEuwlSSQCCfAf7K5Qq-RA] deleting index

[2020-07-06T18:09:14,270][INFO ][o.e.c.m.MetaDataCreateIndexService] [139ed5ecd08c] [magento2*product_8*v2] creating index, cause [api], templates [], shards [1]/[1], mappings []

[2020-07-06T18:09:14,366][INFO ][o.e.c.m.MetaDataMappingService] [139ed5ecd08c] [magento2*product_8_v2/AJNQ5MhrQKev8HiQWS3GDA] create*mapping [document]

[2020-07-06T18:09:15,596][INFO ][o.e.c.m.MetaDataMappingService] [139ed5ecd08c] [magento2*product_8_v2/AJNQ5MhrQKev8HiQWS3GDA] update*mapping [document]

[2020-07-06T18:09:16,649][INFO ][o.e.c.m.MetaDataMappingService] [139ed5ecd08c] [magento2*product_8_v2/AJNQ5MhrQKev8HiQWS3GDA] update*mapping [document>

yellow open magento2*product_8*v2 AJNQ5MhrQKev8HiQWS3GDA 1 1 0 0 71.8kb 71.8kb

@magento-engcom-team magento-engcom-team added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: ready for dev Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Oct 1, 2020
@magento-engcom-team
Copy link
Contributor Author

The issue was exported from the internal JIRA. The link to the original JIRA issue: https://jira.corp.magento.com/browse/MC-35790

@m2-assistant
Copy link

m2-assistant bot commented Oct 1, 2020

Hi @magento-engcom-team. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

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 give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this


⚠️ 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@m2-community-project m2-community-project bot added this to Ready for Grooming in Low Priority Backlog Oct 1, 2020
@magento-engcom-team magento-engcom-team added Component: Other Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch labels Oct 1, 2020
@m2-community-project m2-community-project bot moved this from Ready for Grooming to Ready for Development in Low Priority Backlog Oct 1, 2020
@magento-engcom-team
Copy link
Contributor Author

✅ Confirmed by @magento-engcom-team
Thank you for verifying the issue. Based on the provided information internal tickets MC-35790 were created

Issue Available: @magento-engcom-team, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Oct 1, 2020
@sivaschenko sivaschenko added the CD Issue recommended for the contribution day label Oct 7, 2020
@sidolov sidolov added this to Ready for Development in High Priority Backlog Oct 20, 2020
@ghost ghost removed this from Ready for Development in Low Priority Backlog Oct 20, 2020
@sdzhepa sdzhepa added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Nov 11, 2020
@magento-engcom-team magento-engcom-team added Reported on 2.4.0 Indicates original Magento version for the Issue report. and removed Reported on 2.4.x Indicates original Magento version for the Issue report. labels Nov 16, 2020
@engcom-Alfa engcom-Alfa added Area: APIs Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed and removed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Aug 25, 2021
@github-jira-sync-bot
Copy link

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.magento.com/browse/AC-742

@hostep
Copy link
Contributor

hostep commented Feb 24, 2022

We've seen a similar problem on one of our shops, where sometimes products are not deleted from the Elasticsearch index after a product import where products get deleted on Magento 2.4.3-p1.
We do use https://github.com/Smile-SA/elasticsuite/ on this particular project, so it might also be a bug in that module, but it's hard to say at this moment ...

@sdzhepa or @sidolov or @sivaschenko: is there any news yet around this ticket (MC-35790 or AC-742)? Or do investigations still need to start?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: APIs CD Issue recommended for the contribution day Component: Other Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: ready for dev Reported on 2.4.0 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
High Priority Backlog
  
Ready for Development
Development

No branches or pull requests

6 participants