Is the problem here really the time the om-client spends waiting at node that
is being taken down ?
The only thing the IMM can do to reduce the time waiting is to send a premature
ERR_TIMEOUT.
But htat could be seen as even more confusing for the om-user, to get timeout
earlier than expected.
There is no other error code that can be replied to the user because all other
generally available error
codes such as TRY_AGAIN or NO_RESOURCES have the semantics that nothing was
done.
The IMMND at the client does not know that nothing was done in this case. In
fact probably the request
was successfully processed most times at the other node.
So I dont see the problem you describe as a real problem and even if you insist
it is a real problem
it is certainly a minor problem and even this minor problem has no solution
local to the imm.
If htere is a solution to make this AMF operation more gracefull towards the
om-client requesting it,
then it lies in the AMF. Perhaps the AMF could delay the termination of the
IMMND a bit in this case ?
/AndersBj
________________________________
From: Nagendra Kumar [mailto:[email protected]]
Sent: den 21 maj 2014 10:38
To: [opensaf:tickets]
Subject: [opensaf:tickets] #916 lock-in of payload middleware su times-out and
remains in ENABLED state
Hi Bj,
Immnd was terminated because of lock-in on mw su.
When immnd was terminated, it should notify users(in this case admin user) to
come out of sync call. User shouldn't be in waiting state till timeout.
-Nagu
________________________________
[tickets:#916]<http://sourceforge.net/p/opensaf/tickets/916/> lock-in of
payload middleware su times-out and remains in ENABLED state
Status: unassigned
Milestone: future
Created: Tue May 20, 2014 07:08 AM UTC by surender khetavath
Last Updated: Wed May 21, 2014 08:25 AM UTC
Owner: nobody
changeset : 5270
1) bring up 4 node cluster
2) lock and then lock-in the payload middleware su i.e
"safSu=PL-4,safSg=NoRed,safApp=OpenSAF"
console output
amf-adm lock-in safSu=PL-4,safSg=NoRed,safApp=OpenSAF
error - command timed out (alarm)
syslog on pl-4
May 20 12:19:59 PL-4 osafamfnd[5473]: NO
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' Presence State INSTANTIATED =>
TERMINATING
May 20 12:19:59 PL-4 osaflcknd[5509]: NO Received AMF component terminate
callback, exiting
May 20 12:19:59 PL-4 osafckptnd[5518]: NO Received AMF component terminate
callback, exiting
May 20 12:19:59 PL-4 osafimmnd[5455]: NO Received AMF component terminate
callback, exiting
May 20 12:19:59 PL-4 osafamfnd[5473]: NO
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' Presence State TERMINATING =>
UNINSTANTIATED
May 20 12:19:59 PL-4 osafsmfnd[5483]: NO Received AMF component terminate
callback, exiting
May 20 12:19:59 PL-4 osafmsgnd[5492]: ER Amf Terminate Callback called
May 20 12:19:59 PL-4 osafmsgnd[5492]: NO Received AMF component terminate
callback, exiting
su state:
safSu=PL-4,safSg=NoRed,safApp=OpenSAF
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
________________________________
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/opensaf/tickets/916/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 20, 2014 07:08 AM UTC by surender khetavath
**Last Updated:** Wed May 21, 2014 08:37 AM UTC
**Owner:** nobody
changeset : 5270
1) bring up 4 node cluster
2) lock and then lock-in the payload middleware su i.e
"safSu=PL-4,safSg=NoRed,safApp=OpenSAF"
console output
amf-adm lock-in safSu=PL-4,safSg=NoRed,safApp=OpenSAF
error - command timed out (alarm)
syslog on pl-4
May 20 12:19:59 PL-4 osafamfnd[5473]: NO
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' Presence State INSTANTIATED =>
TERMINATING
May 20 12:19:59 PL-4 osaflcknd[5509]: NO Received AMF component terminate
callback, exiting
May 20 12:19:59 PL-4 osafckptnd[5518]: NO Received AMF component terminate
callback, exiting
May 20 12:19:59 PL-4 osafimmnd[5455]: NO Received AMF component terminate
callback, exiting
May 20 12:19:59 PL-4 osafamfnd[5473]: NO
'safSu=PL-4,safSg=NoRed,safApp=OpenSAF' Presence State TERMINATING =>
UNINSTANTIATED
May 20 12:19:59 PL-4 osafsmfnd[5483]: NO Received AMF component terminate
callback, exiting
May 20 12:19:59 PL-4 osafmsgnd[5492]: ER Amf Terminate Callback called
May 20 12:19:59 PL-4 osafmsgnd[5492]: NO Received AMF component terminate
callback, exiting
su state:
safSu=PL-4,safSg=NoRed,safApp=OpenSAF
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
---
Sent from sourceforge.net because [email protected] is
subscribed to http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
