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

Importing the staged config throws an error: another field with the same name already exists

Posted 3 days 18 hours ago by Francis Greaves (themetman) in How-To and Troubleshooting

Comments Enhanced

Posted 1 week 5 days ago by (izmeez) in How-To and Troubleshooting

Why not add a Github star?

Posted 1 week 6 days ago by (izmeez) in How-To and Troubleshooting

Recent comments

@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...

Posted 3 days 12 hours ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Thanks, I have to go out now, I will try later on and report back

Posted 3 days 17 hours ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....

Posted 3 days 17 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:

Importing the staged config throws an error: another field with the same name already exists