Hi Lennart Agree with your comments, except the following one, I copy it out here for easier follow up: / //3.2.5.2Behavior after headless (client recovery) ////
After headless, client recovery procedure is only started when there is communication with NTF server required to re-establish, which could be executed as instance of consumer (subscriber, reader) or producer (sender)/ [Lennart] Clients will be automatically recovered when the agent has established contact with the NTF server: [Minh] Your comment seems not align with the current implementation, it sounds like agent is about starting recovery thread right after contact with sever is established. My text is not clear also, I mean recovery is only initiated when client Id/subsciptionId/ ReaderId are required re-establish with server after headless. There are many other APIs that do not need server's presence and those ones can be operational with/without server (allocate/free). I guess it should be written again like this ///3.2.5.2Behavior after headless (client recovery) /// // /After headless, client recovery procedure is only started when client needs to reintroduce itself to NTF server, which could be executed as instance of consumer (subscriber, reader) or producer (sender)/ How does this sound to you? / /Thanks, Minh/ / On 11/04/16 21:49, Lennart Lund wrote: > > Hi Minh > > I still have some comment. Please see attached document > > Thanks > > Lennart > > *From:*minh chau [mailto:minh.c...@dektech.com.au] > *Sent:* den 11 april 2016 08:20 > *To:* Lennart Lund; Vu Minh Nguyen; 'praveen malviya' > *Cc:* opensaf-devel@lists.sourceforge.net; Jorge Pacheco Garcia > *Subject:* Re: [devel] Review request for NTF: Update PR doc for cloud > resilience [#1707] V3 > > Hi Lennart, > > I have changed a bit in item 3.2.5 with your idea, please have a look. > > Thanks, > Minh > > ------------------------------------------------------- > > > 3.2.5 Support Loss of Both System Controller Nodes > > Loss of both system controller(SC) nodes means that the NTF service > has lost its server (director). This situation will be named as > “headless” in the rest of this document. > > After headless state, all information that existed in the server on > the SC-nodes is lost. When the SC node(s) are started again after > being in the headless state, the NTF agent will send information about > existing clients to the server so they can be restored. > > Recovery procedure will include the following client's information: > > ·ntfHandle > > ·Notification subscriptions including filters > > ·Reader handle > > However, all logged notifications will be lost. This means that if > reader handle is restored, reader will not be able to read > notifications before headless state. > > > 3.2.5.1Behavior during headless > > The following APIs will return SA_AIS_ERR_TRY_AGAIN until NTF server > is available again, which are: saNtfInitialize, saNtfNotificationSend, > saNtfNotificationSubscribe, saNtfNotificationReadInitialize, and > saNtfNotificationReadNext. > > All remaining APIs (including SaNtfFinalize, > saNtfNotificationUnsubcribe and saNtfNotificationReadFinalize) can be > used during headless. > > > 3.2.5.2 Behavior after headless (client recovery) > > After headless, client recovery procedure is only started when there > is communication with NTF server required to re-establish, which could > be executed as instance of consumer (subscriber, reader) or producer > (sender) > > ·As subscriber: Recovery is started as soon as NTF Agent detects that > NTF Server is up after headless. NTF Agent will send a dummy callback > to subscriber's mailbox to trigger saNtfDispatch call. From > saNtfDispatch, saNtfNotificationSubscribe, or > saNtfNotificationUnsubscribe, Agent will start recovery . > > ·As reader: Recovery is started if client calls > saNtfNotificationReadInitialize, saNtfNotificationReadNext, or > saNtfNotificationReadFinalize. > > ·As sender: Recovery is started if client calls saNtfNotificationSend . > > Once recovery succeeds, client can continue using existing handles to > read or send notifications as well as receive subscribed notifications. > > If recovery fails, the corresponding handle will be invalidated. This > mean that client will get SA_AIS_ERR_BAD_HANDLE. If this happen client > must initialize new handle. > > On 08/04/16 23:15, Lennart Lund wrote: > > Hi Minh, > > The intended reader of this document is a user of the NTF service. This > means that only information that has direct impact on the user should be > written here. > > The easiest way for me to explain what I mean was to rewrite the text > make it a bit shorter and omit some information in the original text. Please > see attached document. > > Thanks > > Lennart > > -----Original Message----- > > From: Vu Minh Nguyen > > Sent: den 8 april 2016 09:37 > > To: Minh Hon Chau; 'praveen malviya'; Lennart Lund > > Cc:opensaf-devel@lists.sourceforge.net > <mailto:opensaf-devel@lists.sourceforge.net> > > Subject: RE: [devel] Review request for NTF: Update PR doc for cloud > > resilience [#1707] > > Hi Minh, > > No comment from me. Ack. > > Regards, Vu. > > -----Original Message----- > > From: minh chau [mailto:minh.c...@dektech.com.au] > > Sent: Thursday, April 07, 2016 7:28 AM > > To: praveen malviya; Lennart Lund; Vu Minh Nguyen > > Cc:opensaf-devel@lists.sourceforge.net > <mailto:opensaf-devel@lists.sourceforge.net> > > Subject: Re: [devel] Review request for NTF: Update PR doc for > cloud > > resilience > > [#1707] > > Hi Lennart, Vu > > This PR doc V2 updates Praveen's comment that changes NTFD to NTFS > > Any comments from you? > > Thanks, > > Minh > > On 06/04/16 18:58, praveen malviya wrote: > > Hi Minh, > > Ack from me with minor comment: NTFD can be changed to NTFS > as in > > readme and code. > > Thanks, > > Praveen > > On 06-Apr-16 11:58 AM, minh chau wrote: > > Hi Lennart, Praveen > > Can you please review the update for #1707? > > One additional item: 3.2.5 > > Thanks, > > Minh > ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel
