Attached is the patch that pushes notifications as job by making imm_ntf_job as
common queue for both imm and ntf. It handles TRY_AGAIN and TIMEOUT in the same
way as it is handled for IMM jobs. Thus AMFD will not get blocked for retrying
to send notification and also it will not log then as error.
There is a discussion in some tickets that notifications should be sent almost
at the same time when AMF updates IMM. Patch improves this behaviour but not
completely.
I think there is already a separate enhacement ticket for moving IMM, NTF, LOG
related things to separate thread(s). So sending notification in separate
could be done in future a part of that enhancement ticket.
Attachments:
-
[314_notificaion.patch](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/d49f7047/3035/attachment/314_notificaion.patch)
(15.7 kB; application/octet-stream)
---
** [tickets:#314] AMF looses alarms and notifications during switch-over**
**Status:** assigned
**Milestone:** future
**Created:** Fri May 24, 2013 08:34 AM UTC by Nagendra Kumar
**Last Updated:** Mon Oct 03, 2016 08:26 AM UTC
**Owner:** Praveen
**Attachments:**
- [messages](https://sourceforge.net/p/opensaf/tickets/314/attachment/messages)
(41.9 kB; application/octet-stream)
- [osafamfd](https://sourceforge.net/p/opensaf/tickets/314/attachment/osafamfd)
(5.7 MB; application/octet-stream)
Migrated from http://devel.opensaf.org/ticket/3051
Background: http://devel.opensaf.org/ticket/3028
If another node (payload) leaves the cluster in the middle of switch-over, amfd
logs this:
Mar 8 10:18:21 SC-1 osafamfd[304]: ER sendStateChangeNotificationAvd:
saNtfNotificationSend Failed (6)
Mar 8 10:18:21 SC-1 osafamfd[304]: ER sendAlarmNotificationAvd:
saNtfNotificationSend Failed (6)
These logs means that amfd failed to send an alarm and a notification due to
TRYAGAIN returned from NTF (in NOACTIVE state)
AMF needs to store the alarms/notifications produced in the NOACTIVE state and
send them at the end of the switch-over. Or with using a separate thread that
can block forever (?) on TRYAGAIN.
The problem exist in all opensaf releases
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
