From 00bc5612a834823d21192a0fc328b53ccf44b0be Mon Sep 17 00:00:00 2001 From: Abhishek Kekane Date: Thu, 9 Feb 2017 11:35:24 +0530 Subject: [PATCH] Release note for _process_unfinished_notifications periodic task Implements: bp add-periodic-tasks Change-Id: I98952acecb842c8498d92a761d6461e750ba52ab --- .../add-periodic-tasks-0c96d6f620502a75.yaml | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 releasenotes/notes/add-periodic-tasks-0c96d6f620502a75.yaml diff --git a/releasenotes/notes/add-periodic-tasks-0c96d6f620502a75.yaml b/releasenotes/notes/add-periodic-tasks-0c96d6f620502a75.yaml new file mode 100644 index 00000000..8b574bcd --- /dev/null +++ b/releasenotes/notes/add-periodic-tasks-0c96d6f620502a75.yaml @@ -0,0 +1,24 @@ +--- +features: + - | + Added _process_unfinished_notifications to process notifications + which are in error or new state. This periodic task will execute at + regular interval defined by new config option + 'process_unfinished_notifications_interval' defaults to 120 seconds. The + notifications which are in ‘new’ status will be picked up based on a new + config option ‘retry_notification_new_status_interval’ defaults + to 60 seconds. + + To change the default execution time of periodic task, following config + option needs to be set with desirable time under 'DEFAULT' section in + 'masakari.conf' file:: + + [DEFAULT] + process_unfinished_notifications_interval = 120 + + To change the default identification time of notifications which are stuck + in 'NEW' state, following config option needs to be set with desirable + time under 'DEFAULT' section in 'masakari.conf' file:: + + [DEFAULT] + retry_notification_new_status_interval = 60