- **Type**: defect --> enhancement
- **Milestone**: 4.5.2 --> 4.7-Tentative
- **Comment**:
This is an enhancement not a defect.
There is no vilation of interface or behavior on the imm part related to this
ticket.
Any IMM call can result in TRY_AGAIN and particularly calls going remote.
This call is no exception.
The fact that this call is currently "over sensitive" to fevs overload is not a
defect.
Fevs overload occurs only because OpensaF has no overload protection or load
regulation
mechanism. So the fact that it occurs is itself a problem or a stress test.
---
** [tickets:#1445] imm: Don't check for pending fevs when updating pure runtime
attributes**
**Status:** review
**Milestone:** 4.7-Tentative
**Created:** Thu Aug 13, 2015 09:48 AM UTC by Hung Nguyen
**Last Updated:** Fri Aug 14, 2015 05:49 AM UTC
**Owner:** Neelakanta Reddy
When invoking saImmOiRtObjectUpdate(), number of pending fevs messages is
always checked on server side and TRY_AGAIN is returned when it reaches
IMMSV_DEFAULT_FEVS_MAX_PENDING.
If the attributes to be updated are pure runtime attributes, number of pending
fevs messages should not be checked because the IMMD_EVT_ND2D_OI_OBJ_MODIFY
message wouldn't be sent out to broadcast to other IMMNDs.
---
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
