AMF will support this attrbiute. Depending upon its value there will be change in behavior when a component enters into instantiation failed state:
1) saAmfNodeFailfastOnInstantiationFailure=1: AMF should failfast the node on which the component has entered into inst_failed state. Here SU will not be marked INST_FAILED fast.
2)saAmfNodeFailfastOnInstantiationFailure=0: Here if a component enters inst_failed state and remain in the same after all retries, its SU will be marked as inst_failed. This inst_failed state of SU and component will be cleared when admin performs REPAIR operation or if AMF performs the repair if enabled. The state will not cleared even if node goes for reboot in between.
changeset: 6347:e2273ff016d6
tag: tip
user: praveen.malviya@oracle.com
date: Fri Mar 13 09:45:46 2015 +0530
summary: amfd : support for saAmfNodeFailfastOnInstantiationFailure [964]
Will raise a separate ticket for TODO part 2).
AMF PR doc changes in changeset:
changeset: 149:7db7d054b191
tag: tip
parent: 146:f6b6282eb97e
user: praveen.malviya@oracle.com
date: Tue Apr 07 15:41:31 2015 +0530
summary: amf: update for 4.6 release [#1169, #1158, #964, #1153, #1235]