This repository has been archived by the owner on Jan 30, 2024. It is now read-only.
2.11.1.65
- Rucio traces
- The transfer protocol returned from the Rucio API is now reported with traces
- Requested by A. Forti, T. Beermann
- Trace report issues in jobs with remote input
- Fixed issue with messed up appid when middleware container was used (resulted in “--eventservicemerge=False” being added to appid)
- Fixed localSite and remoteSite values that became mixed up due to changes inside the middleware container (updated ddmendpoint in combination with a Rucio env variable that is not known inside the container) - this lead to the wrong values ending up in the base trace report which is only updated and sent after the middleware container and remote file verification have finished
- Reported by I. Vukotic
- The transfer protocol returned from the Rucio API is now reported with traces
- Raythena related updates
- New pilot options added to facilitate Raythena testing (previously pilot config file had to be manually merged after pilot release with config changes)
- -u (no value - turn off payload proxy verification; default is True when -u is not specified)
- -v (number of getjob requests; default is 2)
- --es-executor-type (event service executor; generic or raythena)
- Removed executor_type, maximum_getjob_requests, payload_proxy_from_server, use_middleware_container from Pilot config (not needed, set in CRIC)
- Pilot can now use a set env variable PILOT_LOGFILE to determine name of log, instead of job definition. Useful when the pilot is interrupted
- The log creation function may now be used (easily) by an external user (read: Harvester)
- New pilot options added to facilitate Raythena testing (previously pilot config file had to be manually merged after pilot release with config changes)
- Fix for killing payload process after receiving tobekilled server command
- Reported by M. Borodin
- Will not kill runpilot2-wrapper.sh process at the end if labelled as an orphan
- Problem seen at RAL
- Reported by J. Walder
- Discussed in ticket https://ggus.eu/index.php?mode=ticket_info&ticket_id=151098
- Support for new task parameter to control looping jobs
- The field ‘noLoopingCheck’ can now be used on the task level to instruct the Pilot to skip the looping payload check
- Looping job documentation: https://github.com/PanDAWMS/pilot2/wiki/Special-Algorithms-and-Functionalities
- Initial versions of s3 and gs copy tools
- Buckets are currently hardcoded, i.e. needs further development
- Pilot Xcache service
- The Pilot may now launch a local xcache service on the WN, in an effort to solve problems with direct access on some sites (e.g. CYFRONET)
- Currently activated via catchall, with a dedicated CRIC option to come
- Documentation: https://github.com/PanDAWMS/pilot2/wiki/Xcache
- Direct access updates
- Added davs to schema list to allow such replicas in direct access
- Corrected usage of allowed schemas for direct access over WAN (full schema list was used, should only be ‘root’ and ‘davs’)
- Requested by R. Walker, A. Anisenkov
- The Pilot is now sending a list of supported CPU instruction sets to the server
- Currently only checking for AVX2, but any other set (or all sets) can be added
- The info is sent with updateJob for the time being (eventually it will be sent with getJob to be used for brokering)
- HPO payloads
- The Pilot now resets the output file list after the pre-process has finished with no more HPO points available, to solve a problem with missing output (which will not exist when the pre-process finishes with exit code 160 in the first iteration)
- Debug mode update
- In the debug mode, the Pilot sends a tail of the latest updated payload log every five minutes to the server
- From this version, the tail will be from the last updated non-binary file, instead of any .log or log. file
- Requested by R. Walker