- **status**: assigned --> review
---
** [tickets:#3015] Amf: node can not join the cluster**
**Status:** review
**Milestone:** 5.19.03
**Created:** Fri Mar 01, 2019 04:34 AM UTC by Thang Duc Nguyen
**Last Updated:** Fri Mar 01, 2019 09:00 AM UTC
**Owner:** Thang Duc Nguyen
When the pbe was hung on ACTIVE SC, a PL node start then stop then start at
during that time.
The AMF will be TIMEOUT when update runtime in the first start. After timeout,
AMFD on ACTIVE will process event and it can process the events in the below
order and it causes the PL can not join the cluster.
- clm_track_cb was called to process the first node down event.
- clm_track_cb was called to process the node up event.
- avd_mds_avnd_down_evh was called to first amfnd down event -> it sets PL NOT
a member of cluster.
- So the PL was stucked with the below message
*2019-02-26 14:11:36.879 SC-1 osafamfd[285]: NO Received nodeup from 2040f:
msgid 1
2019-02-26 14:11:36.880 SC-1 osafamfd[285]: WA Not a Cluster Member dropping
the msg
2019-02-26 14:11:37.985 SC-1 osafamfd[285]: NO Received nodeup from 2040f:
msgid 1
2019-02-26 14:11:37.986 SC-1 osafamfd[285]: WA Not a Cluster Member dropping
the msg
2019-02-26 14:11:39.079 SC-1 osafamfd[285]: NO Received nodeup from 2040f:
msgid 1
2019-02-26 14:11:39.081 SC-1 osafamfd[285]: WA Not a Cluster Member dropping
the msg*
In this case, increase the priority amfnd down event subscribe by AMFD can make
the PL was rebooted and can re-join the cluster.
---
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