After exploring multiple option we finalized the approach of sending
`node_name` as a part of standard SEND() message MDS header and sending
node_name each message is Expensive and transport performance issue, so we are
cautiously implementing optimized solution.
We will be publishing the fist Version of the #1522 patch by first week
of February ( this week end 05/Feb/2016 ), but In-service upgrade ,
optimization , review comments of first patch will be included in second
Version of the patch.
---
** [tickets:#1522] MDS: Include node name as a part of control events**
**Status:** accepted
**Milestone:** 5.0.FC
**Created:** Tue Oct 06, 2015 03:20 PM UTC by Mathi Naickan
**Last Updated:** Thu Jan 28, 2016 06:34 AM UTC
**Owner:** A V Mahesh (AVM)
It can be noted that currently the MDS NODE_UP event is one of the evidences
that CLM uses to determine and permit a node to join the cluster. Currently
node_id and ipaddress information is sent as a part of NODE_UP event.
However, it is now desired to send node_name also as a part of the MDS control
events for use in the following two scenarios:
a) CLM uses this as additional information to correlate NODE_UP event. i.e. CLM
can match node_name(part of NODE_UP) configured on that with the node_name
configured in the imm.xml. (This will be additional check on top of what CLMNA
provides ofcourse)
b) Some services that are started before CLM(like LOG service has come up with
a case #1480) require to know about node_name for logging the origination
information. This information has to be ideally read using CLM APIs but that is
not possible in scenarios when the membership of a node has not yet been
decided or this information will not be retrievable for logging activities that
takes place during the time when the cluster formation/synchronization is still
in progress.
It has to be seen whether MDS can send node_name as a part of standard MDS
header or as a part of MDS service up event (SVC_UP event) or as a part of MDS
NODE_UP event.
[It appears that sending node_name as a part of service up event (i.e. SVC_UP
event ) is more straightforward from the MDS user's perspective, but needs more
study]
---
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.
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
