Inhibit haystack update during import #23

New issue

Closed

opened 2021-02-12 12:23:41 +01:00 by nik · 3 comments

nik commented

2021-02-12 12:23:41 +01:00

(Migrated from edugit.org)

Haystack currently updates the haystack index for every saved object upon receiving a post_save signal.

We should inhibit this during mass import, as it clogs up the Celery workers with thousands of jobs.

Part of the solution would be to refactor the use of database transactions throughout the LDAP import.

Haystack currently updates the haystack index for every saved object upon receiving a `post_save` signal. We should inhibit this during mass import, as it clogs up the Celery workers with thousands of jobs. Part of the solution would be to refactor the use of database transactions throughout the LDAP import.

nik commented

2021-02-12 12:30:11 +01:00

(Migrated from edugit.org)

mentioned in issue AlekSIS-Core#371

nik commented

2021-02-14 02:22:21 +01:00

(Migrated from edugit.org)

mentioned in merge request !104

nik commented

2021-06-18 15:52:26 +02:00

(Migrated from edugit.org)

Celery tasks are globally delayed until commit now, so anything that is wrapped in a transaction (like the various parts of the LDAP import) are as well.

nik (Migrated from edugit.org) closed this issue

2021-06-18 15:52:27 +02:00