Red Hat Bugzilla – Bug 1028487
Recovery alert cache refresh needs to happen prior to alert notification processing
Last modified: 2013-11-13 18:06:29 EST
Currently alert notifications are processed in the same transaction as the alert creation, recovery alert activation, etc. There are a few issues related to the notif processing taking place in this transaction:
1) It simply extends the length of an already complicated transaction, potentially holding locks, delaying the alert commit, delaying the global cache refresh flags being committed (such that HA servers can pick up on it), etc...
2) Notifications can actually initiate recovery actions such as executing resource operations, invoking CLI scripts, etc. This should not happen prior to our ability to update the global alert condition cache, which must happen to begin condition matching on activated recovery alert definitions. Otherwise we risk an actual recovery happening prior to the recovery alert being ready.
The alert notification processing should happen outside of the alert creation transaction and after cache refresh.
master commit 28becd282f8cd3ed4327a56ea0c08f8431845dba
Author: Jay Shaughnessy <email@example.com>
Date: Fri Nov 8 10:42:46 2013 -0500
Restructure SLSB methods (locals only, no remote changes) to process alert
notifications later in the workflow, after the alert is committed and after
we have a chance to update the condition caches (for more reliable recovery
alerting). Needed to be able to pass back the new alert through the call chain.