Magento – How to solve indexer status “suspended” (n in backlog)

indexingmagento2magento2.2

One of the indexers that are configured to be updated on schedule is locked in the state "suspended" and does not get updated anymore.

Output of bin/magento indexer:status

+----------------------------+------------------+-----------+-------------------------------+---------------------+
| Title                      | Status           | Update On | Schedule Status               | Schedule Updated    |
+----------------------------+------------------+-----------+-------------------------------+---------------------+
| ...                        |                  |           |                               |                     |
| IntegerNet_Solr            | Reindex required | Schedule  | suspended (101028 in backlog) | 2018-09-24 15:28:44 |
| ...                        |                  |           |                               |                     |
+----------------------------+------------------+-----------+-------------------------------+---------------------+

Others show idle (0 in backlog) and the current time in the "Schedule Updated" column, so the indexer schedule is generally working.

How can I solve this?

Best Answer

I found out, that the status is set in \Magento\Framework\Mview\View::suspend() and removed in \Magento\Framework\Mview\View::resume().

These methods are only called in \Magento\Indexer\Model\Indexer::reindexAll() to suspend the scheduled indexing before a forced full reindexing and to resume it afterwards or if an exception occurs.

But if the process is terminated without exception, e.g. killed, segfaulted or even runs into a non-recoverable fatal error, the status stays "suspended" and there are no means to resume it.

Solution: make sure, there really is no full reindex running, then update the status via SQL.

You'll find all the statuses with:

select * from mview_state;

and update it like this:

update mview_state set status='idle' where view_id='integernet_solr';

Related Solutions

Magento – Locking indexer programmatically

You could just touch the lock file.

<?php touch('BP.DS.'var'.DS.'locks'.DS.'index_process_1.lock')

#!/bin/bash
touch /home/path/public_html/var/locks/index_process_1.lock

This is obviously a low quality solution - but if you wanted to perform this action peripherally to Magento (eg. from a bash script, it would be suitable).

Otherwise, the methods you need are in Mage_Index_Model_Process

Such as isLocked(), lockAndBlock(), and unlock()

Assuming your module extends said class, you need only declare

const PROCESS_ID = 'my_indexer'

And use the methods as appropriate

$this->lockAndBlock();

Magento – Indexer model is not defined

Most probably you have a declared indexer that does not have a model associated to it. There is also the chance that if you have the cache enabled, this cache can be corrupted. (but I doubt it). Just to make sure first you clear the contents of var/cache.
If that does not work, and probably won't here is how the indexes work. An index is defined in the config.xml of a module. Here is an example.

<index>
   <indexer>
        <catalog_product_attribute>
            <model>catalog/product_indexer_eav</model>
        </catalog_product_attribute> 
         ..............
    </indexer>
</index>

This declares an index with code catalog_product_attribute. As you can see there is a model tag inside it. That is the model that should handle the index. This is what is missing for one of your indexes.
To see which one is wrong do this:

In the method Mage_Index_Model_Process::getIndexer(), above the line:

Mage::throwException(Mage::helper('index')->__('Indexer model is not defined.'));

Add this debug line:

echo $code;exit;

and try to access the index grid again. This should show you the index with problems. Check the config.xml files for a tag with the same name as the value you get from the code above. Look specially in the extensions that you recently installed.

Best Answer

Related Solutions

Magento – Locking indexer programmatically

Magento – Indexer model is not defined

Related Topic