- **status**: accepted --> review
---
** [tickets:#2015] mds: Use a separate process for writing MDS logs**
**Status:** review
**Milestone:** 5.2.FC
**Created:** Fri Sep 09, 2016 09:59 AM UTC by Anders Widell
**Last Updated:** Fri Sep 09, 2016 09:59 AM UTC
**Owner:** Anders Widell
Currently, the MDS log entries are written to disk from within the MDS code.
This file I/O is done while holding the MDS mutex, and can potentially block
for a long time if file I/O is slow. In the best case, it will result in longer
latency for MDS messages. In the worst case, it will result in an overflow of
the TIPC receive buffer and loss of incoming MDS messages.
To avoid this problem, the idea is to let a separate process (one per node) do
all the MDS logging file I/O. The MDS library will send log messages to this
logger process using a UNIX socket. Incidentally, there is already a separate
process osaf-transport-monitor which is responsible for rotating the MDS logs.
This process can get the added responsibility to not only rotate the log files,
but also write the log entries to the disk.
---
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
