- **status**: review --> fixed
- **Comment**:
changeset: 5722:d353ca39b3d9
tag: tip
parent: 5718:1388c9d98536
user: Neelakanta Reddy <[email protected]>
date: Thu Sep 04 19:33:04 2014 +0530
summary: imm:Return TRY_AGAIN if implemeter is not yet discarded [#946]
changeset: 5721:607c54388bd6
branch: opensaf-4.5.x
parent: 5715:4944d006ca9f
user: Neelakanta Reddy <[email protected]>
date: Thu Sep 04 19:33:04 2014 +0530
summary: imm:Return TRY_AGAIN if implemeter is not yet discarded [#946]
changeset: 5720:7721b51a7fb0
branch: opensaf-4.4.x
parent: 5690:5b7e510e8eea
user: Neelakanta Reddy <[email protected]>
date: Thu Sep 04 19:33:04 2014 +0530
summary: imm:Return TRY_AGAIN if implemeter is not yet discarded [#946]
changeset: 5719:dd9d4300a5a4
branch: opensaf-4.3.x
parent: 5689:17325a76ea56
user: Neelakanta Reddy <[email protected]>
date: Thu Sep 04 19:33:04 2014 +0530
summary: imm:Return TRY_AGAIN if implemeter is not yet discarded [#946]
---
** [tickets:#946] IMM: implementerset is returning ERR_EXISTS with new OI
handle, when the old OI hadle is finalized because of BAD_HANDLE**
**Status:** fixed
**Milestone:** 4.3.3
**Created:** Thu Jun 26, 2014 01:04 PM UTC by Neelakanta Reddy
**Last Updated:** Thu Sep 04, 2014 11:07 AM UTC
**Owner:** Neelakanta Reddy
The problem is observed in 70 node setup when IMMSV_DEFAULT_FEVS_MAX_PENDING
has value 16.
1. Implementer is set for an OI handle (AMFD)
2. rtobjupdate is called with OI handle, the rtupdate got TIMEOUT (The reason
may be IMMD is too busy processing other FEVS messages)
3. another rtobjupdate is called for the OI handle, In this IMM will return
with the following error.
ERR_BAD_HANDLE: Handle use is blocked by pending reply on syncronous call
4. AMFD agent finalizes OI handle.
5. AMFD agent tries to initialize again and sets new OI handle.
6. Implementer is set for an new OI handle, with the same implementer-name
ERR_EXISTS is returned
saImmOiImplementerSet failed 14
Here the ERR_EXISTS returned for the following reasons:
a. Because OIfinalizing of the OI handle, An FEVS message is sent to clear the
implementer.
b. FEVs message is sent from local IMMND to active IMMD and active IMMD
broadcast the message to all IMMND.
c. Before the broadcast FEVS message arrived from IMMD, the AMFD tries to set
the implementer again with the same name and ERR_EXISTS is returned.
The solution may be if the implementer is marked as dying and an implementer
set has arrived before clearing it in iMMNDs, then TRY_AGAIN will be returned.
---
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.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
