I don't think this is good enough. Just increasing timeouts seems like giving
up accepting a bad system design. What about CLM clients? They will not get any
answers in 40 secs.
I see some options:
1. CLM does not use LOG
2. Standby LOG & NTF open the log stream so that at failover it will just write
3. Backport the LOG server change from 4.4 (multithread LOG)
option 2 seems reasonable to me
---
** [tickets:#720] Increase csisetcallback timeout value for services using LOG
API(eg:- CLM, NTF) **
**Status:** review
**Labels:** csisetcallbacktimeout MDS api timeout 10 seconds
**Created:** Wed Jan 15, 2014 10:14 AM UTC by Mathi Naickan
**Last Updated:** Wed Jan 29, 2014 08:36 PM UTC
**Owner:** Mathi Naickan
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.
Now, in the worst case scenario, the saflog() internal utility can take 30
seconds before returning.
This ticket proposes that the csisetcallbacktimeout is increased to 40 seconds
for users of LOG in 4.2 and 4.3.
---
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.
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets