Direct access and the Pilots


This document describes how direct access is handled by the different pilot versions.


This section describes under which circumstances the pilot uses direct access.

AGIS settings respected by the Pilots

In general, direct access for a given queue can be controlled with the direct_access_lan and direct_access_wan AGIS settings. See the table below for information.

AGIS parameter Explanation
direct_access_lan Boolean; if set to True, the queue allows for direct access over LAN. For production jobs, the PanDA server will broker transferType=direct jobs to the queue.
direct_access_wan if set to True, the queue allows for direct access over WAN.

Specially Requested Access Mode in Job Parameters

The following job parameter options instructs the pilot to force an access mode:

Job parameter option Explanation
--accessmode=copy Copy to scratch
--accessmode=direct Direct access

Supported File Formats and Schemas

The file formats supported for direct access is not restricted by the pilots, but limited: the pilot allows any file format to be considered for direct access unless the file name contains the patterns '.tar.gz', '.lib.tgz' or '.raw.'. Normally this should mean that ROOT files are left.

The following replica schemas are allowed: 'root://', 'dcache://', 'dcap://', 'https://' and 'file://'.

Note: if prodDBlockToken in the job definition is set to 'local', direct access will be switched off.

Direct Access in Pilot 1

The mechanism for direct access is different for production versus user jobs. Below follows a description of the different cases.

Direct Access in Production Jobs

Direct access mode for production jobs are defined by the transferType='direct' job definition parameter. Such a job will be generated if the allowInputLAN='only' is set on the task definition level.

For production jobs that use direct access, the pilot swaps the LFN:s from the job parameters to corresponding TURL:s, as returned by the list_replicas() function.

Direct Access in User Jobs

Direct access in user jobs are normally controlled by AGIS. The user can switch off direct access on a given site with the --forceStaged prun/pAthena option for special needs. The user can also request only sites with direct access turned on by using the --useDirectIOSites option.

Furthermore, a commonly used HammerCloud option is the --accessmode job parameter (see above), which is used to force tasks to either use direct access or copy-to-scratch. This is an internally used pilot instruction, so the pilot remove the option from the job parameters before the payload is executed.

When a user job is going to use direct access, the pilot adds --usePFCTurl option to the prun/pAthena command.

Direct Access in Pilot 2

As of September 2018, direct access support in Pilot 2 works in the same way as in Pilot 1.

-- PaulNilsson - 2018-05-23

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2018-11-26 - PaulNilsson
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    PanDA All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback