Development repository updated.
---
** [tickets:#9] LOG: decouple from file system characteristics**
**Status:** accepted
**Created:** Mon May 06, 2013 08:57 AM UTC by elunlen
**Last Updated:** Tue Jun 04, 2013 01:32 PM UTC
**Owner:** elunlen
Merged from devel (#3003)
Currently the LOG server process (osaflogd) is single threaded. This means that
if this single thread is hanging in a write() system call, it cannot answer to
AMF health checks or LOG client requests for initialize, open etc.
With a single thread, the AMF healthcheck timeout takes the meaning of
supervising the file system itself. That should not be the responsibility of
the LOG service.
There are two (or more?) alternatives:
1) create one thread per stream. This stream should be responsible for all file
system operation of one stream. The main thread will
2) using async io (man 7 aio) keeping a single thread
the advantage of 1) is that makes it rather easy to have flow control per
stream by means of a size limited mailbox per stream.
not sure how the same could be achieved with aio.
After this change, AMF healthchecks, initialize and stream open/close should
"never" be blocked like it can be today.
---
Sent from sourceforge.net because you indicated interest in
<https://sourceforge.net/p/opensaf/tickets/9/>
To unsubscribe from further messages, please visit
<https://sourceforge.net/auth/subscriptions/>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
