This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
*newbie* /dev/root full after 24hrs
#45
(2018-08-08, 03:36 PM)tkurki Wrote: How about a watchdog thread  that closes connections that the client has closed (that are in CLOSE_WAIT), no matter what?

Not that simple.  Each connection in kplex has its own thread and each thread is responsible for all the data associated with that connection.  If you simply close the socket the next client connection will re-use the closed file descriptor which its (old) controlling thread doesn't realise has been closed under it and gets you into a world of pain.  Better to signal the controlling thread to die but then this is becomes a non-trivial architectural change.

Again, this is not ideal and hands up, no output with thousands of unfulfilled clients was not a scenario I considered, but a kludge as a workaround while awaiting a complete re-architecture is probably the most straight forward solution here.
Reply


Messages In This Thread
*newbie* /dev/root full after 24hrs - by Yannick - 2018-06-06, 06:27 PM
*newbie* /dev/root full after 24hrs - by tkurki - 2018-08-05, 02:41 PM
RE: *newbie* /dev/root full after 24hrs - by stripydog - 2018-08-15, 09:33 PM
*newbie* /dev/root full after 24hrs - by PaddyB - 2018-08-06, 11:39 PM

Forum Jump:


Users browsing this thread: 2 Guest(s)