- **status**: assigned --> review
---
** [tickets:#3164] osaf: enhance vm frozen detection in tcp.plugin**
**Status:** review
**Milestone:** 5.20.05
**Created:** Thu Mar 05, 2020 09:20 AM UTC by Thuan Tran
**Last Updated:** Thu Mar 05, 2020 09:20 AM UTC
**Owner:** Thuan Tran
If a vm is frozen for real, we will have the diff of two timestamp reading at
arb greater than self.timeout
but if the diff of two timestamp reading at arb greater than self.timeout, it
is not 100% sure the vm is frozen.
It is correct to reboot the active SC if the active SC's VM is frozen for real,
since active SC loses 'real' connectivity towards arb (TCP) and peer SC. The
problem is that tracking timestamp at arb does not differentiate a real frozen
vm or a high load at arbitrator node.
If it is only the node hosting arbi being overloaded, it is not ok to reboot
the active SC.
---
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
