- **status**: review --> fixed
- **Milestone**: 5.19.07 --> 5.22.06
- **Comment**:
commit e4fdf7487e7a3fb01d7c79c6d604c435ee8c9652 (HEAD -> develop,
origin/develop, ticket-3040)
Author: thang.d.nguyen <[email protected]>
Date: Wed Jan 18 09:35:52 2023 +0700
amf: reboot to recover from mismatch msg id [#3040]
There is a case that mismatch messge id between
AMFND and active AMFD. It causes the system unhealthy
(partial assigned).
Reboot the node that message mismatched to recover
the system.
---
** [tickets:#3040] Amfnd: reboot if mismatch msg id b/w amfd and amfnd**
**Status:** fixed
**Milestone:** 5.22.06
**Created:** Thu May 16, 2019 07:33 AM UTC by Thang Duc Nguyen
**Last Updated:** Fri Jan 27, 2023 11:46 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 [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._______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
