Understanding the Magento 2 index Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Why wasn't the Product Attributes Index Included in the Scheduled Updates in 1.13?Need SEO help with our sitemap.xml Google Index rateDisabled product remains in catalog_category_product index (Magento Enterprise)catalog_category_product index corrupts once in a dayReindexing option not available in magento 2.0what is mview in magento2?What does each entry in index management actually do?What causes an indexer to get marked as “Scheduled” in EEMagento2 reindex via cron jobTemporarily disable reindexing
How to write capital alpha?
Test print coming out spongy
Why not send Voyager 3 and 4 following up the paths taken by Voyager 1 and 2 to re-transmit signals of later as they fly away from Earth?
How to ask rejected full-time candidates to apply to teach individual courses?
Rationale for describing kurtosis as "peakedness"?
If Windows 7 doesn't support WSL, then what is "Subsystem for UNIX-based Applications"?
Does the Black Tentacles spell do damage twice at the start of turn to an already restrained creature?
Was Kant an Intuitionist about mathematical objects?
Google .dev domain strangely redirects to https
What is the difference between a "ranged attack" and a "ranged weapon attack"?
Why do early math courses focus on the cross sections of a cone and not on other 3D objects?
Is multiple magic items in one inherently imbalanced?
Can two people see the same photon?
Printing attributes of selection in ArcPy?
A term for a woman complaining about things/begging in a cute/childish way
How were pictures turned from film to a big picture in a picture frame before digital scanning?
Weaponising the Grasp-at-a-Distance spell
The Nth Gryphon Number
Moving a wrapfig vertically to encroach partially on a subsection title
After Sam didn't return home in the end, were he and Al still friends?
What does it mean that physics no longer uses mechanical models to describe phenomena?
White walkers, cemeteries and wights
How to change the tick of the color bar legend to black
What does the writing on Poe's helmet say?
Understanding the Magento 2 index
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Why wasn't the Product Attributes Index Included in the Scheduled Updates in 1.13?Need SEO help with our sitemap.xml Google Index rateDisabled product remains in catalog_category_product index (Magento Enterprise)catalog_category_product index corrupts once in a dayReindexing option not available in magento 2.0what is mview in magento2?What does each entry in index management actually do?What causes an indexer to get marked as “Scheduled” in EEMagento2 reindex via cron jobTemporarily disable reindexing
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Generally Magento's index can be updated in 3 ways (depending on usage and configuration):
- "On Save"
- "By Schedule"
- Using
indexer:reindexcommand
This is what I can gather from the description in the official documentation for each of these ways:
- The index will be updated immediately when e.g. a product is changed in the back end and saved.
- According to the graphic of the Indexing types in the documentation, when editing and saving a product, entries are made in a changelog table (via MySQL triggers). Magento's
cron:runcommand (which would be set up to run every minute by default) will then index those changed products. - This command will update the complete index.
Just for clarification I want to know if the following is true for each of the 3 ways of updating the index:
- The index is updated "On Save" only for the affected data (i.e. the changed product), not the whole index (which would take very long).
- The index is only updated for the changed products (should be obvious).
- The index is updated for all products, regardless of whether they have been changed or not.
And to clarify further: is it true, that the only way to update the index only for changed products is via "On Save" or via "By Schedule" plus cron:run?
magento2 reindex indexing index
asked Apr 16 at 14:54
fritzmgfritzmg
245112
add a comment |
Generally Magento's index can be updated in 3 ways (depending on usage and configuration):
- "On Save"
- "By Schedule"
- Using
indexer:reindexcommand
This is what I can gather from the description in the official documentation for each of these ways:
- The index will be updated immediately when e.g. a product is changed in the back end and saved.
- According to the graphic of the Indexing types in the documentation, when editing and saving a product, entries are made in a changelog table (via MySQL triggers). Magento's
cron:runcommand (which would be set up to run every minute by default) will then index those changed products. - This command will update the complete index.
Just for clarification I want to know if the following is true for each of the 3 ways of updating the index:
- The index is updated "On Save" only for the affected data (i.e. the changed product), not the whole index (which would take very long).
- The index is only updated for the changed products (should be obvious).
- The index is updated for all products, regardless of whether they have been changed or not.
And to clarify further: is it true, that the only way to update the index only for changed products is via "On Save" or via "By Schedule" plus cron:run?
magento2 reindex indexing index
asked Apr 16 at 14:54
fritzmgfritzmg
245112
add a comment |
Generally Magento's index can be updated in 3 ways (depending on usage and configuration):
- "On Save"
- "By Schedule"
- Using
indexer:reindexcommand
This is what I can gather from the description in the official documentation for each of these ways:
- The index will be updated immediately when e.g. a product is changed in the back end and saved.
- According to the graphic of the Indexing types in the documentation, when editing and saving a product, entries are made in a changelog table (via MySQL triggers). Magento's
cron:runcommand (which would be set up to run every minute by default) will then index those changed products. - This command will update the complete index.
Just for clarification I want to know if the following is true for each of the 3 ways of updating the index:
- The index is updated "On Save" only for the affected data (i.e. the changed product), not the whole index (which would take very long).
- The index is only updated for the changed products (should be obvious).
- The index is updated for all products, regardless of whether they have been changed or not.
And to clarify further: is it true, that the only way to update the index only for changed products is via "On Save" or via "By Schedule" plus cron:run?
magento2 reindex indexing index
asked Apr 16 at 14:54
fritzmgfritzmg
245112
Generally Magento's index can be updated in 3 ways (depending on usage and configuration):
- "On Save"
- "By Schedule"
- Using
indexer:reindexcommand
This is what I can gather from the description in the official documentation for each of these ways:
- The index will be updated immediately when e.g. a product is changed in the back end and saved.
- According to the graphic of the Indexing types in the documentation, when editing and saving a product, entries are made in a changelog table (via MySQL triggers). Magento's
cron:runcommand (which would be set up to run every minute by default) will then index those changed products. - This command will update the complete index.
Just for clarification I want to know if the following is true for each of the 3 ways of updating the index:
- The index is updated "On Save" only for the affected data (i.e. the changed product), not the whole index (which would take very long).
- The index is only updated for the changed products (should be obvious).
- The index is updated for all products, regardless of whether they have been changed or not.
And to clarify further: is it true, that the only way to update the index only for changed products is via "On Save" or via "By Schedule" plus cron:run?
magento2 reindex indexing index
magento2 reindex indexing index
asked Apr 16 at 14:54
fritzmgfritzmg
245112
asked Apr 16 at 14:54
fritzmgfritzmg
245112
edited Apr 16 at 15:17
fritzmg
asked Apr 16 at 14:54
fritzmgfritzmg
245112
asked Apr 16 at 14:54
fritzmgfritzmg
245112
asked Apr 16 at 14:54
fritzmgfritzmg
245112
245112
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Reindex On Save - The Reindex will take place in real time when a change is saved in backend. It will be fine for small websites with a few admin users.
Reindex On Schedule - Reindex will be scheduled to take place via cronjobs accordingly. It will be suitable for stores with huge data and many admin users. If you have set reindex to occur every one hour, if you are making any change in the backend your change will be applied in the frontend within a maximum period of 1 hour.
indexer:reindex - When you want to reindex all indexers we can use this command.Ex: If a reindex gets locked we can reset the indexer and use this command to reindex all indexers.
Both Reindex On Save and Reindex On Schedule can be used to update the index of changes stores. You can choose between the two based on your store size and frequency of changes made to products.
answered Apr 17 at 10:26
Raj Mohan RRaj Mohan R
673110
add a comment |
Since posting the question, I found a few articles that explain Magento's indexing mechanic in a little more detail. One of the more detailed one is https://www.bigbridge.nl/blog/essential-magento-2-partial-reindexing/
This essentially confirms my questions:
- regardless of how you update a product (back end, REST API or direct SQL queries for example), the
indexer_update_all_viewscron job will update the index for the changed products (when set to "By Schedule"). indexer:reindexwill always update the complete index, not just for the changed entities.
answered Apr 17 at 10:50
fritzmgfritzmg
245112
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f270353%2funderstanding-the-magento-2-index%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Reindex On Save - The Reindex will take place in real time when a change is saved in backend. It will be fine for small websites with a few admin users.
Reindex On Schedule - Reindex will be scheduled to take place via cronjobs accordingly. It will be suitable for stores with huge data and many admin users. If you have set reindex to occur every one hour, if you are making any change in the backend your change will be applied in the frontend within a maximum period of 1 hour.
indexer:reindex - When you want to reindex all indexers we can use this command.Ex: If a reindex gets locked we can reset the indexer and use this command to reindex all indexers.
Both Reindex On Save and Reindex On Schedule can be used to update the index of changes stores. You can choose between the two based on your store size and frequency of changes made to products.
answered Apr 17 at 10:26
Raj Mohan RRaj Mohan R
673110
add a comment |
Reindex On Save - The Reindex will take place in real time when a change is saved in backend. It will be fine for small websites with a few admin users.
Reindex On Schedule - Reindex will be scheduled to take place via cronjobs accordingly. It will be suitable for stores with huge data and many admin users. If you have set reindex to occur every one hour, if you are making any change in the backend your change will be applied in the frontend within a maximum period of 1 hour.
indexer:reindex - When you want to reindex all indexers we can use this command.Ex: If a reindex gets locked we can reset the indexer and use this command to reindex all indexers.
Both Reindex On Save and Reindex On Schedule can be used to update the index of changes stores. You can choose between the two based on your store size and frequency of changes made to products.
answered Apr 17 at 10:26
Raj Mohan RRaj Mohan R
673110
add a comment |
Reindex On Save - The Reindex will take place in real time when a change is saved in backend. It will be fine for small websites with a few admin users.
Reindex On Schedule - Reindex will be scheduled to take place via cronjobs accordingly. It will be suitable for stores with huge data and many admin users. If you have set reindex to occur every one hour, if you are making any change in the backend your change will be applied in the frontend within a maximum period of 1 hour.
indexer:reindex - When you want to reindex all indexers we can use this command.Ex: If a reindex gets locked we can reset the indexer and use this command to reindex all indexers.
Both Reindex On Save and Reindex On Schedule can be used to update the index of changes stores. You can choose between the two based on your store size and frequency of changes made to products.
answered Apr 17 at 10:26
Raj Mohan RRaj Mohan R
673110
Reindex On Save - The Reindex will take place in real time when a change is saved in backend. It will be fine for small websites with a few admin users.
Reindex On Schedule - Reindex will be scheduled to take place via cronjobs accordingly. It will be suitable for stores with huge data and many admin users. If you have set reindex to occur every one hour, if you are making any change in the backend your change will be applied in the frontend within a maximum period of 1 hour.
indexer:reindex - When you want to reindex all indexers we can use this command.Ex: If a reindex gets locked we can reset the indexer and use this command to reindex all indexers.
Both Reindex On Save and Reindex On Schedule can be used to update the index of changes stores. You can choose between the two based on your store size and frequency of changes made to products.
answered Apr 17 at 10:26
Raj Mohan RRaj Mohan R
673110
answered Apr 17 at 10:26
Raj Mohan RRaj Mohan R
673110
answered Apr 17 at 10:26
Raj Mohan RRaj Mohan R
673110
answered Apr 17 at 10:26
Raj Mohan RRaj Mohan R
673110
673110
add a comment |
add a comment |
Since posting the question, I found a few articles that explain Magento's indexing mechanic in a little more detail. One of the more detailed one is https://www.bigbridge.nl/blog/essential-magento-2-partial-reindexing/
This essentially confirms my questions:
- regardless of how you update a product (back end, REST API or direct SQL queries for example), the
indexer_update_all_viewscron job will update the index for the changed products (when set to "By Schedule"). indexer:reindexwill always update the complete index, not just for the changed entities.
answered Apr 17 at 10:50
fritzmgfritzmg
245112
add a comment |
Since posting the question, I found a few articles that explain Magento's indexing mechanic in a little more detail. One of the more detailed one is https://www.bigbridge.nl/blog/essential-magento-2-partial-reindexing/
This essentially confirms my questions:
- regardless of how you update a product (back end, REST API or direct SQL queries for example), the
indexer_update_all_viewscron job will update the index for the changed products (when set to "By Schedule"). indexer:reindexwill always update the complete index, not just for the changed entities.
answered Apr 17 at 10:50
fritzmgfritzmg
245112
add a comment |
Since posting the question, I found a few articles that explain Magento's indexing mechanic in a little more detail. One of the more detailed one is https://www.bigbridge.nl/blog/essential-magento-2-partial-reindexing/
This essentially confirms my questions:
- regardless of how you update a product (back end, REST API or direct SQL queries for example), the
indexer_update_all_viewscron job will update the index for the changed products (when set to "By Schedule"). indexer:reindexwill always update the complete index, not just for the changed entities.
answered Apr 17 at 10:50
fritzmgfritzmg
245112
Since posting the question, I found a few articles that explain Magento's indexing mechanic in a little more detail. One of the more detailed one is https://www.bigbridge.nl/blog/essential-magento-2-partial-reindexing/
This essentially confirms my questions:
- regardless of how you update a product (back end, REST API or direct SQL queries for example), the
indexer_update_all_viewscron job will update the index for the changed products (when set to "By Schedule"). indexer:reindexwill always update the complete index, not just for the changed entities.
answered Apr 17 at 10:50
fritzmgfritzmg
245112
answered Apr 17 at 10:50
fritzmgfritzmg
245112
answered Apr 17 at 10:50
fritzmgfritzmg
245112
answered Apr 17 at 10:50
fritzmgfritzmg
245112
245112
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f270353%2funderstanding-the-magento-2-index%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
