/* * Copyrights : CNRS * Author : Oleg Lodygensky * Acknowledgment : XtremWeb-HEP is based on XtremWeb 1.8.0 by inria : http://www.xtremweb.net/ * Web : http://www.xtremweb-hep.org * * This file is part of XtremWeb-HEP. * * XtremWeb-HEP is free software: you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation, either version 3 of the License, or * (at your option) any later version. * * XtremWeb-HEP is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with XtremWeb-HEP. If not, see . * */ ******************************************** * XWHEP-7.6.3 * *------------------------------------------* * Release date : Oct 23rd, 2011 * * Author : Oleg Lodygensky * * lodygens@lal.in2p3.fr * * Trac : https://trac.lal.in2p3.fr/DGHEP * ******************************************** Developments are tracked on our trac server referred above. -A- Corrections -A.1- usage of Zipper.java modified so that we now use file name only for entries having a path starting with a '/' or containing "../" (e.g. "/var/log/dummy.log" is compressed as "dummy.log"; "/home../var/log/dummy.log" too) -A.2- a bug corrected in Zipper.java so that compressed results by the worker don't start with '/' any more -A.3- to avoid misbehavior, a worker not presenting a version equaling the server one receives no job -B- New features - none - -C- Known Bugs -C.1- Result download errors reported using 'xwdownload', but not with 'xwresult' We have not been able to reproduce them If you encounter these, please send us log file in DEBUG mode -C.2- xtremweb.gmond.pl does not scale -C.3- the scheduler is not fair -C.4- there may be some concurrent access problems leading to some errors There may be two concurrent accesses problems - on server side, DB access may lead to inconsistency between works and tasks tables This could certainly be solved using SQL transactions But we would then need MySQL >=5 There are sime issues withe transactions with hsqldb - on worker side, file access if a worker is configured to run jobs in parallel (default one thread per CPU core) We have observed that these concurrent access problems may lead to up to 6% erroneous jobs. Until further notification, we consider this rate acceptable. - Versionning - Versionning is as follow - X is a major part of the version - Y is a minor part of the version - Z is the micro part of the version (*) X reports a very important change : for example the communication protocol changes or a major new feature is modified/introduced/removed When X changes, backward compatibility is not ensured (*) Y reports a important but not critical change : backward compatibility is ensured (*) Z reports a minor change : bug correction, documentation changes etc.