- **status**: review --> fixed
- **assigned_to**: Minh Hon Chau --> nobody
- **Comment**:
commit 72ff674dea7f796b8d957ed7ecaccb0d404f6360
Author: Minh Chau <[email protected]>
Date: Thu Nov 22 10:19:58 2018 +1100
amfd: Do not create absent assignment if number of assignment exceeds
[#2968]
---
** [tickets:#2968] amfd: Do not create absent assignment if excessive
assignments exist**
**Status:** fixed
**Milestone:** 5.18.12
**Created:** Wed Nov 21, 2018 03:54 AM UTC by Minh Hon Chau
**Last Updated:** Wed Nov 21, 2018 11:32 PM UTC
**Owner:** nobody
In the situation of network merges back from partitioning, both active SCs
clash and go reboot. All payloads join back cluster from SC absence mode. Now,
the new active amfd will look up in IMM to create absent (active) assignments
and failover to the present (standby) assignments. This is the way that amfd
recovers from SC absence. However, there are also excessive assignments due to
the network partitioning (#2929). In this cases, once excessive assignment is
detected, amfd does not need to create absent assignments.
---
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
