mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #51484
[Bug 1778889] Re: Dropping and re-adding elasticsearch triggers will prevent other triggers from executing if some action is made during this period.
We are looking to move away from explicit triggers as it's not easy to
deal with turning them off for certain processes (like upgrading large
sites) but rather have equivalent php code
** Changed in: mahara
Status: New => Confirmed
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1778889
Title:
Dropping and re-adding elasticsearch triggers will prevent other
triggers from executing if some action is made during this period.
Status in Mahara:
Confirmed
Bug description:
On big sites there is an issue regarding the time it takes cron to run
due to the use of triggers/procedures on the tables when processing
information for elasticsearch.
A solution was developed to drop triggers for this portion of the cron
run and then re-enable triggers.
The issue is that other triggers cannot be executed during the period
of disabling triggers and re-enabling them.
Relevant Bugs:
https://bugs.launchpad.net/mahara/+bug/1731067?comments=all
https://bugs.launchpad.net/mahara/+bug/1778888
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1778889/+subscriptions
References