activeeon-bot
commented
13 years ago Original comment posted by Christian Delbé on 15, Nov 2010 at 17:59 PM
Workaround for release 2.2.0 : set pa.rm.selection.maxthreadnumber=1 in rm settings.ini file.
Closed activeeon-bot closed 9 years ago
activeeon-bot
commented
13 years ago Original comment posted by Christian Delbé on 15, Nov 2010 at 17:59 PM
Workaround for release 2.2.0 : set pa.rm.selection.maxthreadnumber=1 in rm settings.ini file.
activeeon-bot
commented
13 years ago Original comment posted by Christian Delbé on 21, Nov 2010 at 17:12 PM
The MAX_SELECTION_THREAD_NUMBER=1 does not work due to SCHEDULING-868 . When several tasks with the SAME select script are submitted, several nodes are asked to the RM => BEST_PROX is used => script is ran and ALL available nodes.
TEMPORARILY FIXED BY r17947
activeeon-bot
commented
13 years ago Original comment posted by Christian Delbé on 22, Nov 2010 at 20:37 PM
Another issue is the fact that several selection scripts for a single task are always ALL executed. For MatLab scripts with side effects, these scripts must be executed SEQUENTIALLY, i.e. the execution is stopped at the first false script.
activeeon-bot
commented
13 years ago Original comment posted by Christian Delbé on 23, Jun 2011 at 09:03 AM
MatLab selection scripts do not start any process anymore, as they rely on LicenseSaver since 3.1.
Original issue created by Oleg Smirnov on 10, Nov 2010 at 11:34 AM - SCHEDULING-883
Mathlab selection scripts perform not only checking of some parameters on hosts but also configure them (launch some processes) for the further job execution. If the node is not used for targeted job these processes remain alive. Currently the resource manager performs the cleanup on the level of node before providing it for computations (kills all active objects on the node). The processes luanched by scripts are not taken into account.
As workaround such scripts should be executed sequentially.