[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
- **status**: review --> fixed - **Comment**: changeset: 8259:1b8f7e298cfb branch: opensaf-5.0.x tag: tip user:Gary Lee date:Wed Oct 26 10:30:23 2016 +1100 summary: amfnd: ignore healthcheck failure if comp is terminating [#1950] changeset: 8258:4ee9197c0147 branch: opensaf-5.0.x parent: 8253:270e4576f185 user:Gary Lee date:Wed Oct 26 10:15:53 2016 +1100 summary: amfnd: ignore healthcheck failure if comp is terminating [#1950] changeset: 8257:6f09e098918c branch: opensaf-5.1.x parent: 8254:810708384cfe user:Gary Lee date:Wed Oct 26 10:13:16 2016 +1100 summary: amfnd: ignore healthcheck failure if comp is terminating [#1950] changeset: 8256:b88de404e0ae user:Gary Lee date:Wed Oct 26 10:12:24 2016 +1100 summary: amfnd: ignore healthcheck failure if comp is terminating [#1950] --- ** [tickets:#1950] Amf: cleanup command is called during termination after health check failure** **Status:** fixed **Milestone:** 5.0.2 **Created:** Fri Aug 12, 2016 09:38 AM UTC by Nagendra Kumar **Last Updated:** Tue Oct 25, 2016 02:27 AM UTC **Owner:** Gary Lee Steps to reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
- **status**: unassigned --> review - **assigned_to**: Gary Lee --- ** [tickets:#1950] Amf: cleanup command is called during termination after health check failure** **Status:** review **Milestone:** 5.0.2 **Created:** Fri Aug 12, 2016 09:38 AM UTC by Nagendra Kumar **Last Updated:** Tue Sep 20, 2016 05:58 PM UTC **Owner:** Gary Lee Steps to reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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.-- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
- **Milestone**: 4.7.2 --> 5.0.2 --- ** [tickets:#1950] Amf: cleanup command is called during termination after health check failure** **Status:** unassigned **Milestone:** 5.0.2 **Created:** Fri Aug 12, 2016 09:38 AM UTC by Nagendra Kumar **Last Updated:** Wed Aug 17, 2016 10:27 AM UTC **Owner:** nobody Steps to reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
May be "Opensaf can allow component to configure to ignore health check failure during termination." --- ** [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:48 PM UTC **Owner:** nobody Steps to reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
I think that the terminate callback should not be monitored by healthcheck. --- ** [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:42 PM UTC **Owner:** nobody Steps to reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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.-- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
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 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:22 PM UTC **Owner:** nobody Steps to reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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.-- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
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 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:35 PM UTC **Owner:** nobody Steps to reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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.-- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
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 **Owner:** nobody Steps to reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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.-- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
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 **Milestone:** 4.7.2 **Created:** Fri Aug 12, 2016 09:38 AM UTC by Nagendra Kumar **Last Updated:** Fri Aug 12, 2016 10:04 AM UTC **Owner:** nobody Steps to reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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.-- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
- Description has changed: Diff: --- old +++ new @@ -11,6 +11,6 @@ -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. -2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination failure or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. +2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- ** [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 reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination command or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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.-- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1950 Amf: cleanup command is called during termination after health check failure
--- ** [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 reproduce -- When NPI component is in termination state and health check also running concurrently, then there is rare chance that health check may return failure because of inability of component to respond during termination. In such case, after healtch check(HC) reported failure, Amf is sending the cleanup command to the component. Observed behaviour -- During cleanup command, there may be contention of resources and there are fair chances that cleanup command uses fiorceful termination of component resulting in generating core dump. Expected behaviour -- The expected behavious can be either of : 1.Amf detecting that HC failure during component termination is a false alarm and ignore the error and ler termination command succeed and then let the rest follows. 2. Amf runs clean up command as explained in the description above. This is because of inability of Amf to detect wherther health check is because of termination failure or because of genuine issue that component was undergoing and it has reported HC failure just after issuing of terminate command. If Amf doesn't take any action then there is likely possibility of termination command timeout as erraneous component can't be trusted. This will delay the repair and recovery for configured timeout period. This is unwanted for sure. Please note that PI component is also being cleaned up in the similar way. So, we need to converge the understanding and evaluate which one is better solution from use case point of view. --- 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.-- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
