As Magento releases 2.X version, I found _replica tables, particularly in the Magento_Catalog module may be for indexing the catalog data.

I also notice that _replica is nothing but the duplicate structure of the respective table in database nature but it means a lot for Magento 2 framework for read and write operational activities I guess.

I want to know that which operations Magento 2 application will consider for _replica tables for Magento_Catalog, CatalogRule and CatalogInventory module.



Replica tables are mainly used for indexer optimization. Replica tables are used to prevent deadlocks or wait locks caused by read/write collisions on the same table.

In the above causes, Magento uses a separate table for reading and write operations and indexing. As a result of this switching process, customer can freely navigate to the category pages, search pages and user layered navigation pages filtered with price when you run full reindexing in the CLI.

If you feel my answer is correct and helps you, please accept and upvote it.

Thank you.

  • Thank you very much for all the people who upvoted for my answer. Dec 26 '18 at 7:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.