I am faced with an issue, whereby after updating magento to 220.127.116.11 from 18.104.22.168 my
catalog_url_rewrite index is stuck on processing. Checking process list I cannot see anything untoward. Also, checking status via shell I see running. Why after updating a store would the reindex now be stuck on processing?
Checking the table catalog_product_index_eav there is no data in there at all. Now, I am not sure if this should be empty or not. But, this was also empty before the update.
I have also tried to reindex via shell same result.
The php error cropping up is:
Allowed memory size of 268435456 bytes exhausted (tried to allocate 130968 bytes) in /magento/app/code/core/Zend/Db/Select.php on line 281
Now, my memory limit has not been changed whatsoever and is in fact at the 256mb I set. On my local I even set the limit to a rather massive 3GB to test, yet the same result.
What could be causing this from the update? On the same server I also have a 22.214.171.124 version, and the reindex completed within 30 seconds.
To rule out database issues I have ran the database repair tool against a fresh new install:
And, as seen there are no issues at all with database.
"...Database doesnt require changes" (db repair tool, 2018)
I even disabled all local extensions in local.xml:
But, the same thing occurs: It runs for awhile then blanks out, and in the php log you can see the above memory size exhausted issue. Rather perplexed as I am not sure what is happening here now.
Interestingly, when I click any product and hit save, I can see that the catalog url rewrite index has been reindex, without the aforementioned issue.
Running the following query I get 196120 rows in the table:
SELECT COUNT(url_rewrite_id) FROM core_url_rewrite;
- 23389 of which are defined as custom;
- And 172722 of which are defined as system.
I am contemplating truncating as a solution. Thus, is it safe to do so, and what are the ramifications?