Improve the way search (re)indexing works.

When initiating a search index re-indexing, we should actually initiate the creation of a new, temporary index in the background (on cron runs).
While the (re)indexing happens in the background, the old index will still be used so that there is no "downtime".
Once the new index is done, we replace the old one with it.
Once the old index is replaced with the new and no errors have occurred, we delete the old index.

GitHub Link:

https://github.com/backdrop/backdrop-issues/issues/1337

GitHub Issue #:

1337

Log in or register to post comments

Recent topics

Field deleted, but: machine-readable name is in use?

Posted 25 min 14 sec ago by RS Snyder (theflightrs) in How-To and Troubleshooting

Field deleted, but: machine-readable name is in use?

Posted 48 min 25 sec ago by RS Snyder (theflightrs) in How-To and Troubleshooting

How to order a view by its aggregated value

Posted 6 hours 4 min ago by Robert Garrigos (robertgarrigos) in How-To and Troubleshooting

Recent comments

I read this quickly, so I'm sure I'm missing something. Check your active config folder. Fields have two components: Database tables Field info and field...

Posted 20 min 27 sec ago by Alejandro Cremaschi (argiepiano) on:

Field deleted, but: machine-readable name is in use?

BTW, this is still a problem in the D7 version (despite what that issue said), so I'm not sure this is possible. I'll have to look more closely into it.

Posted 28 min ago by Alejandro Cremaschi (argiepiano) on:

How to order a view by its aggregated value

Hmm... I was able to reproduce this issue when I thought it would work. Wuold you mind opening an issue in the queue?

Posted 1 hour 1 min ago by Alejandro Cremaschi (argiepiano) on:

How to order a view by its aggregated value