Re: [devel] [PATCH 1 of 1] osaf: increase csisetcallback timeout for services using saflog (CLM, NTF) [#720]

[Hans F. <han...@er...>]

Alternatively the standby process just logs some message at start. That should  do the trick too

If you go the other path please keep saflog as it is and add an additional init function


Skickat från min Sony Xperia™-smartphone


---- Mathivanan Naickan Palanivelu skrev ----

Well there is an option 4(not sure if we are talking about the same, i.e. your option 2) that can work well within the framework of 4.2 and 4.3 systems.

Option 4): Split saflog() into safloginit() and saflogwrite() i.e. move the synchronous calls loginitialize, streamopen to safloginit() and safloginit() has to be done much early in the lifecycle of the LOG user/client. i.e. CLM, NTF, AMF both ACTIVE and STANDBY instances.
This can indeed be additionally done, in the context of this ticket. Will take a stab at that.

Having said that, if we discuss the theory part
a) i don't think increasing the csisetcallback will in reality create any functional problem for the clients of CLM or NTF because, the mode of service provided to these clients are asynchronous in nature i.e. such subscribers(clients) are not held up on a blocking call! And as such, for runtime changes, saflog is attempted by these serviceproviders(CLM, NTF) only after doing their core job, i.e. servicing their subscribers(like sending subscription/track callbacks) first and then they try to update the IMM and/or send notifications and/or log it to saflog.

b) A client's HA timeout should indeed be greater than the system defined timeout value of an API(say, the blocking variants).  In the worst caes scenarios, there is a realistic chance for the serviceconsumer getting a TIMEOUT when requesting a service(API). However, upon timeout if this client retries later, the call would indeed succeed.

Cheers,
Mathi.

----- han...@er... wrote:

> See comment in ticket
> /Hans
>
> On 01/17/2014 11:41 AM, mat...@or... wrote:
> >   osaf/services/saf/clmsv/config/clmsv_objects.xml |  4 ++--
> >   osaf/services/saf/ntfsv/config/ntfsv_objects.xml |  2 +-
> >   2 files changed, 3 insertions(+), 3 deletions(-)
> >
> >
> > It has been observed (in pre 4.4) on field that a client of LOG (in
> the specific case - CLM,
> > but in general all LOG API users) can get blocked when calling
> saflog() or LOG()
> > because the LGS was busy doing a file operation.
> > The current MDS API timeout is 10 seconds and the csisetcallback
> timeout for
> > all(except SMF has about 30 seconds) services is 10 seconds.
> > in the worst case scenario, the saflog() internal utility can take
> 30 seconds before returning,
> > i.e. saflog internally calls three synchronous apis.
> > This patch changes the csisetcallback timeout to 40 seconds.
> >
> > diff --git a/osaf/services/saf/clmsv/config/clmsv_objects.xml
> b/osaf/services/saf/clmsv/config/clmsv_objects.xml
> > --- a/osaf/services/saf/clmsv/config/clmsv_objects.xml
> > +++ b/osaf/services/saf/clmsv/config/clmsv_objects.xml
> > @@ -30,7 +30,7 @@
> >              </attr>
> >              <attr>
> >                      <name>saAmfCtDefCallbackTimeout</name>
> > -                   <value>10000000000</value>
> > +                   <value>40000000000</value>
> >              </attr>
> >              <attr>
> >                      <name>saAmfCtRelPathInstantiateCmd</name>
> > @@ -126,7 +126,7 @@
> >              </attr>
> >              <attr>
> >                      <name>saAmfCtDefCallbackTimeout</name>
> > -                   <value>10000000000</value>
> > +                   <value>40000000000</value>
> >              </attr>
> >              <attr>
> >                      <name>saAmfCtRelPathInstantiateCmd</name>
> > diff --git a/osaf/services/saf/ntfsv/config/ntfsv_objects.xml
> b/osaf/services/saf/ntfsv/config/ntfsv_objects.xml
> > --- a/osaf/services/saf/ntfsv/config/ntfsv_objects.xml
> > +++ b/osaf/services/saf/ntfsv/config/ntfsv_objects.xml
> > @@ -19,7 +19,7 @@
> >              </attr>
> >              <attr>
> >                      <name>saAmfCtDefCallbackTimeout</name>
> > -                   <value>10000000000</value>
> > +                   <value>40000000000</value>
> >              </attr>
> >              <attr>
> >                      <name>saAmfCtRelPathInstantiateCmd</name>
> >
> >
> ------------------------------------------------------------------------------
> > CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> > Learn Why More Businesses Are Choosing CenturyLink Cloud For
> > Critical Workloads, Development Environments & Everything In
> Between.
> > Get a Quote or Start a Free Trial Today.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Opensaf-devel mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensaf-devel
> >