The solution implemented is the following:
When FM is stopped with opensafd stop a message is sent to the other peer,
GFM_GFM_EVT_PEER_IS_TERMINATING, this to be able to differntiate between a hung
opensaf node and a "controlled" shutdown of opensaf.
---
** [tickets:#2160] fm: Add support for differentiating a hung node versus a
stopped node **
**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Wed Nov 02, 2016 11:37 AM UTC by Hans Nordebäck
**Last Updated:** Wed Dec 07, 2016 07:51 AM UTC
**Owner:** Hans Nordebäck
At opensafd stop, OpenSAF don't differentiate between a hung node and a stopped
node.
This ticket will implement the suggestion by AndersW from ticket [#2094], to:
1). modify the opensafd script to lock the node using CLM. The CLM lock admin
operation will remove the node from cluster membership.
2).fm_main will then be able to differentiate between a hung node and a stopped
node by checking the node for CLM cluster membership.
---
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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
