In the first hand Non PI, I guess the Non PI is using osafAmfCtRelPathHcCmd
feature for performing health checking and PI probably using the health check
API, it shouldn't differ with respect to this behaviour, so both Non PI and PI
as well, I guess.
---
** [tickets:#1950] Amf: cleanup
Good. So, what do you think about the inability of Amf to decide, whether it is
a true or false error ? Amf doesn't know anything about it. If Amf ignores
error reported, the term callback is going to take time with loss of HA.
---
** [tickets:#1950] Amf: cleanup command is called during
So mean for PI component as well ?
---
** [tickets:#1950] Amf: cleanup command is called during termination after
health check failure**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Fri Aug 12, 2016 09:38 AM UTC by Nagendra Kumar
**Last Updated:** Fri Aug 12, 2016 01:19 PM UTC
If healthcheck and terminate cmd is running in parallel and the healthcheck
fails, AMF should ignore this healthcheck failure, so (1) above is to prefer.
---
** [tickets:#1950] Amf: cleanup command is called during termination after
health check failure**
**Status:** unassigned
Hi MInh,
The case "1)When comp completes assignments in headless state". can still occur
in some cases when AMFNDs have responded for assignmets to AMFD and cluster
becomes headless before AMFD processes these mail box messages. In this case
after headless state, AMFD will get SUSI FSM states
---
** [tickets:#1950] Amf: cleanup command is called during termination after
health check failure**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Fri Aug 12, 2016 09:38 AM UTC by Nagendra Kumar
**Last Updated:** Fri Aug 12, 2016 09:38 AM UTC
**Owner:** nobody
Steps to
- **status**: review --> fixed
- **Comment**:
changeset: 7851:6ba070e84429
tag: tip
user:Hans Nordeback
date:Fri Aug 12 08:15:04 2016 +0200
files: osaf/services/infrastructure/fm/fms/fm_main.c
description:
fm: Enabling remote fencing