On 1/27/2016 5:21 PM, elunlen wrote:
>
> Hi Mahesh,
>
> From our point of view this makes this solution not usable for us. It is
> necessary that it works the same regardless if the underlying protocol is TCP
> or TIPC and it must always work with all nodes. If this can't be solved it
> means that we must use another solution for the log service.
> I suggest two alternatives where CLM is used to get the node name based on
> the node id given via MDS:
>
> Fix CLM so that the initialize API can be used also before the CLM server
> (director) is started. As is today the API call will never return which makes
> the log service hang resulting in a nid timeout. The reason for this is that
> clm initialize api waits for node up for the clm server before returning. If
> this is changed so that initialize instead returns with TRY AGAIN parts of
> the problem is solved. If a log record is requested to be written before CLM
> is started node id (as a string) could temporary be used instead of node name.
>
> A better solution could be to make it possible to start CLM before the
> log service. This is not possible for now since CLM wants to use NTF which is
> dependent on LOG.
>
> And of course if the problem below somehow can be handled
>
> Thanks
> Lennart
On 1/28/2016 11:46 AM, A V Mahesh wrote:
> Hi Lennart,
>
> Thanks for the alternatives proposals, we will go through your option and
> get back to you on implementation feasibility.
>
> Form MDS point of view, we are exploring whether MDS can send node_name as a
> part of standard MDS header option ,
> this looks possible ,but very Expensive only for one service requirement
> , ether we should send node_name each message of Transport is debatable
> point ,
> even it may lead to transport performance issue by packing & unpacking the
> node name while sending and after receiving .
>
> -AVM
---
** [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:** Wed Jan 27, 2016 03:41 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
