I have a theory about why you see the long delay.
Are you using the tool immadm to generate the admin-operation ?
If so, then I think you are spending all those seconds in a
TRY_AGAIN lopp inside the immadm client.
Thus it is not actually any successfully invoked admin-operation
that is taking so long to be processed in the server.
Rather it is the tool that is shielding you from its delays in
setting admin-owner need for the admin-op. Duryng the sync etc reulting
from the restarted SC.
You can enable imma client side trace by defining: IMMA_TRACE_PATHNAME
before invoking immadm to see what it is doing. Although I cant promise
that it clearly traces its retry behavior.
---
** [tickets:#889] unknown: oi poll timeout differs during switchover and
failover scenarios**
**Status:** unassigned
**Milestone:** future
**Created:** Wed May 07, 2014 03:10 PM UTC by surender khetavath
**Last Updated:** Thu May 08, 2014 08:15 AM UTC
**Owner:** nobody
changeset : 5143.
test:
1) in a thread do oiInit()
2) oiImplSet() & OiObjectImplSet on an object
3) oiselectionObjectGet()
4) poll() on the fd
In the main thread
1) om init, ownerset,
2) invoke controller failover/switchover
3) AdminOp(ONE_SECOND) on the object
If the poll timeout value is 40secs, then OI doesn't receive AdminOp callback
and poll timesout.
If the poll timeout value is increased to say 80secs, then OI gets AdminOp
callback.
How does it differ?
1) is the imm operation held until failover is completed?
2) is the imm operation held until the failed node re-joins?
3) The time to receive cbk i.e more than 40secs is not acceptable for HA.
The same test using swithover succeeds i.e receives cbk under 20secs of poll
timeout.
two versions of logs attached
---
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.
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
