Trace of AMFD, AMFND attached

Attachments:

- 
[osafamfd.7z](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/f57e4c222f/b408/attachment/osafamfd.7z)
 (14.1 MB; application/octet-stream)
- 
[osafamfnd.7z](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/f57e4c222f/b408/attachment/osafamfnd.7z)
 (7.0 MB; application/octet-stream)


---

** [tickets:#3040] Amfnd: clm track start not called if mismatch received 
message id b/w amfd and amfnd when node failover **

**Status:** assigned
**Milestone:** 5.19.06
**Created:** Thu May 16, 2019 07:33 AM UTC by Thang Duc Nguyen
**Last Updated:** Thu May 16, 2019 07:37 AM UTC
**Owner:** Thang Duc Nguyen


During SC failover, message received on ACTIVE AMFD can not be checked point to 
AMFD on STANDBY SC. But the AMFND still process the message ack for that 
message then it remove from queue. 
STANDBY SC takes ACTIVE and mismatch message id b/w AMFD and AMFND on new 
ACTIVE. As consequence, clm track start can not invoked to update cluster 
member nodes if these node was rebooted.  

Need to reboot recovery if received message  id of amfd mismatch with sent 
message id of amfnd.


---

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

Reply via email to