- **status**: review --> fixed
- **Comment**:
commit 37bd253efec52d924eb0757fe6ce049f5a264d86 (HEAD -> release,
origin/release)
Author: Anders Widell <a...@..com>
Date: Mon Nov 20 13:46:17 2017 +0100
base: Send logtrace message in blocking mode to avoid dropped messages
[#2637]
Add a the possibility to select between blocking and non-blocking send and
receive operations on the UnixSocket, and use blocking mode when sending
logtrace trace messages. Trace messages will thus not be lost, but excessive
tracing can slow down the service being traced. This patch also contains a
small
optimization to reduce the size of each trace log message, by avoiding fixed
field widths and redundant characters.
---
** [tickets:#2637] base: Trace messages can be dropped**
**Status:** fixed
**Milestone:** 5.18.01
**Created:** Thu Oct 19, 2017 10:13 AM UTC by Anders Widell
**Last Updated:** Mon Nov 13, 2017 03:26 PM UTC
**Owner:** Anders Widell
Since the new logtrace implementation uses non-blocking send, trace messages
may be dropped in case a large amount of trace messages are generated in a
burst. The suggestion is to use blocking send instead, to avoid loss of trace
messages.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
