Magento Commerce, 2.0.11

Magento 2.0.18 is the final 2.0.x release. After March 2018, Magento 2.0.x will no longer receive security patches, quality fixes, or documentation updates. To maintain your site's performance, security, and PCIPayment Card Industry: Refers to debit and credit cards and their associated businesses. compliance, upgrade to the latest version of Magento.

Index Management

Magento reindexes automatically whenever one or more items change. Actions that trigger reindexing include price changes, creating catalog or shopping cartA grouping of products that the customer wishes to purchase at the end of their shopping session. price rules, adding new categories, and so on. To optimize performance, Magento accumulates data into special tables using indexers. As the data changes, the indexed tables must be updated—or reindexed. Reindexing is performed as a background process, and your store remains accessible during the processes.

Reindexing the data reduces the time the customer has to wait. For example, if you change the price of an item from $4.99 to $3.99, Magento reindexes the data to show the price change in the store. Without indexing, Magento would have to calculate the price of every product on the fly—taking into account shopping cart price rules, bundle pricing, discounts, tier pricing, and so on. Loading the price for a product might take longer than the customer is willing to wait.

The indexers can be set to either update on save, or on schedule. Reindexing is performed as a background process that is scheduled as a cron job, and your store remains accessible during the processes. A system message appears if a cron job is not available to update any indexers that become invalid.

Index Management

Index Management has a slightly different presentation for the following configurations:

  • Solr full-text catalog search
  • Flat product catalog

To avoid problems when multiple AdminThe password-protected back office of your store where orders, catalog, content, and configurations are managed. users update objects that trigger automatic reindexing, we recommend that you set all indexers to run on schedule as cron jobs. Otherwise, every time an object is saved, any objects with interdependencies might cause a deadlock. Symptoms of a deadlock include high CPU usage and MySQL errors. As a best practice, we recommend that you use scheduled indexing.

To change the index mode:

1. On the Admin sidebarThe right or left column of a two-column page layout., tap System. Then under Tools, choose Index Management.
2. Mark the checkbox of each indexer that you want to change.
3. Set Actions to one of the following:
  • Update on Save
  • Update by Schedule
4. Tap Submit to apply the change to each selected indexer.
  • Column Descriptions




    The name of the indexer.


    A description of the indexer.


    Indicates the current update mode for each indexer. Options:

    Update on Save

    The index is set to update whenever a change is saved.

    Update on Schedule

    The index is set to update on schedule according to a cron job.


    Displays one of the following:


    The index is up-to-date.


    Reindexing is scheduled to take place.


    Reindexing is currently running.

    Reindex Required

    A change has been made that requires reindexing, but the indexers cannot be updated automatically. Check to see if cron is available and configured correctly.


    Indicates the date and time an index was last updated.