qrun still hangs for me. Never on the first run though. In 5 of 6 tries, it hangs on the 3rd run. On other it hanged on 2nd run. 3rd parameter always 6.
I don't think I ever breeched memory/swap issues in these or previous tests. I found a way to unhang it though. start 2nd jqt session, and run qrun in it. It may hang, but other session will unfreeze. If it did hang, then repeat in other session until both unfrozen. Though, doing this enough can result in both sessions frozen (especially if using uneven task balances)... A 3rd jqt session to the rescue of both frozen ones. the show command and immediate jqt console output is a nice change. ________________________________ From: Eric Iverson <[email protected]> To: Programming forum <[email protected]> Sent: Tuesday, October 3, 2017 5:41 PM Subject: [Jprogramming] jcs/zmq addons updated A few cosmetic changes and perhaps fixes for qrun and related task problems. Note: qrun now defined in jcs/qrun.ijs The main problem was that a task ending could have a delayed close of the associated socket port and this could, depending on timing, prevent the proper start of the next task trying to use the same port. The jcs sockets now set LINGER 0. This should avoid that class of problem. Initial stress tests all run clean on Linux and Windows. The other problem was that a server errror in qrun caused a hang. This wouldn't happen normally if the jobs were well defined and ran to completion. A way to trigger the qrun server error in Windows was to run a large number of tasks with large (memory consumption) jobs. This could exhaust windows swap memory and get an out-of-memory error. qrun now catches the server error, reports the lse error, and continues. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
