Since #946624: Use a cron queue for indexing got in, the „Index now“ function on indexes' „Status“ tabs has become a bit useless, as it will only index those items that weren't already queued for indexing in cron (which might still take days or weeks). The solution is probably to first consume the items from the cron queue, and only then request new ones from the data source controller.

Other solutions, patches or thoughts on this welcome!

Comments

drewish’s picture

On one site I've got it got totally stalled. It's calling search_api_index_items() which returns 0 meaning it's not doing anything but because the remaining stuff keeps showing up it keeps trying. I'm guessing they're all stuck in the queue some place. I guess I need to figure out how to clear the queue so it starts over.