changeset:   5116:f3705e8f90fc
branch:      opensaf-4.3.x
parent:      5113:dab0d4067b90
user:        Nagendra Kumar<[email protected]>
date:        Tue Apr 08 13:19:02 2014 +0530
summary:     amfd: return TRY_AGAIN for su/node lockin op if su pres state is 
not appropriate [#807]

changeset:   5117:24c5651c6639
branch:      opensaf-4.4.x
parent:      5114:9dbafd1322b9
user:        Nagendra Kumar<[email protected]>
date:        Tue Apr 08 13:30:57 2014 +0530
summary:     amfd: return TRY_AGAIN for su/node lockin op if su pres state is 
not appropriate [#807]

changeset:   5118:be04892c8ef3
tag:         tip
parent:      5115:257088744782
user:        Nagendra Kumar<[email protected]>
date:        Tue Apr 08 13:31:20 2014 +0530
summary:     amfd: return TRY_AGAIN for su/node lockin op if su pres state is 
not appropriate [#807]

[staging:f3705e]
[staging:24c565]
[staging:be0489]



---

** [tickets:#807] AMF returns TRYAGAIN for saAmfRegister**

**Status:** review
**Milestone:** future
**Created:** Thu Mar 06, 2014 03:52 PM UTC by Hans Feldt
**Last Updated:** Fri Apr 04, 2014 08:54 AM UTC
**Owner:** Nagendra Kumar

Use case: node lock followed by node lock instantiation, During node lock a 
component causes an SUfailover followed by repair of the component which means 
instantiation.

So we have a component in state INSTANTIATING when the SU terminate request 
comes. AMF then (silently) escalates this to execute cleanup of the already 
instantiating component and changes its state to TERMINATING. Due to timing the 
cleanup script does not find any process to kill and returns 0. At the same 
time the instantiate script starts a process that calls saAmfRegister which 
returns TRYAGAIN because the component is in TERMINATING state.

Suggestions:
- AMF should probably return BAD-OPERATION in this case (is there any valid 
case where it should return TRYAGAIN?)
- the reason for escalating to cleanup should be logged

Finally, should AMF really start a second CLC CLI script while it knows one is 
already running? This implies that the cleanup script must be able to kill the 
instantiate script which is not stated in the specification besides I haven't 
any such script. So maybe AMF should kill the child process executing the 
instantiate script before it starts cleanup. This is a change in "core" since 
there is no interface to do this.




---

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.
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to