After the introduction of collections and bulk match-making, which represented an effective optimisation on real-life use-cases, the efficacy of the match-making and the WM in general needs to affect not only large collections but also single jobs, among which resubmissions and pending are typically found. Prior to the present release single job processing was done almost serially, because of "big" locks on wide accessed data structures. This redesign will also allow for faster operations on the ISM, such as dumping or updating.
The so-called Task Queue is replaced by a prioritized event queue where requests queues up waiting to be processed in a as stateless as possible fashion (so that several locks have been consequently removed).
Periodic activities, handled as timed events, will re-schedule themselves to show-up at a given time in the ready queue. The number of threads is kept controlled, in such a way that each and every request, whatever kind, is processed by the same thread pool. The WM core becomes essentially a multi-threaded function executor, without the clear-cut dispatcher/request handler distinction.
- WMPROXY refactoring; TODO
Newly introduced features:
- added support for IPv6
- added support for Grid site DELEGATION 2
- improved error reporting for DAGs
- Dumping the ISM can be done more often at a lesser cost, simply by creating a jobdir request (basically a file) like this one: [ command = "ism_dump"; ]
- run-time selection of LB/LBproxy for each service *TODO
- removed perl code from the jobwrapper
- jobdir enabled as JC/ICE input - as a parameter jdl sandbox transport protocol
- The jw template is now cached at each WM start (restart to re-read it) - CE forward requirements - ISM ... Salvo - curl TODO
- ...
for me:
- some not catched excections: open bug
proxy renewal bug - terminated collections still registered
Bug fixing:
Fix for bug #39903: Fermilab proxy cannot submit to WMS SL4, they are ok with SL3
committed to 3_1_0, 3_2_0 and HEAD
glite-wms-wmproxy_R_3_1_40_1
Fix for bug #39903: Fermilab proxy cannot submit to WMS SL4, they are ok with SL3
committed to 3_1_0, 3_2_0 and HEAD
glite-wms-wmproxy_R_3_1_40_1
Fix for bug #45389: wms proxy certificate expires while the purger is using it
Fix for bug #41720: command glite-brokerinfo without specify option crash
glite-wms-brokerinfo-access_R_3_1_4_1
Fix for bug #43368: Long Nordugrid ARC Jobs go into the HELD state and get resubmitted
committed to 3_1_0 and 3_2_0
Fix for bug #43370: grid job names don't get translated from gLite to Nordugrid ARC submission
Fix for bug #43545: messed up user DN logged by WMProxy
glite-wms-wmproxy_R_3_1_40_1
Fix for bug bug #33103: Request for adding an feature to select only specific VO resources via an additional LDAP filter
Fix for bug bug# 43498 WMS needs more ISM logging
Fix for bug bug #44321 OutputData in the job wrapper should be implemented in terms of lcg-utils
-- MarcoCecchi - 03 Nov 2008
Fix for bug #45389: wms proxy certificate expires while the purger is using it
Fix for bug #41720: command glite-brokerinfo without specify option crash
glite-wms-brokerinfo-access_R_3_1_4_1
Fix for bug #43368: Long Nordugrid ARC Jobs go into the HELD state and get resubmitted
committed to 3_1_0 and 3_2_0
Fix for bug #43370: grid job names don't get translated from gLite to Nordugrid ARC submission
Fix for bug #43545: messed up user DN logged by WMProxy
glite-wms-wmproxy_R_3_1_40_1
Fix for bug bug #33103: Request for adding an feature to select only specific VO resources via an additional LDAP filter
Fix for bug bug# 43498 WMS needs more ISM logging
Fix for bug bug #44321 OutputData in the job wrapper should be implemented in terms of lcg-utils
-- MarcoCecchi - 03 Nov 2008