Looks OK. Perhaps in avd_try_send_notification(), you could change
notificationHandle to a reference, to avoid duplicating"if
(myntf->notificationType == YYY)" twice in that function.
---
** [tickets:#314] AMF looses alarms and notifications during switch-over**
**Status:** fixed
**Milestone:** 5.0.2
**Created:** Fri May 24, 2013 08:34 AM UTC by Nagendra Kumar
**Last Updated:** Fri Nov 18, 2016 11:14 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 opensaf-tickets@lists.sourceforge.net 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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
