-
Notifications
You must be signed in to change notification settings - Fork 42
Open
Description
We had a case where
- A user used the DIRAC JobLaunchpad WebApp specifying a LFN
- The "LFN" specified was not a file, but a directory
- The job started downloading files under the directory, filling up the WN disk
- The site found the problem and closed the WN, then contacted us
JobLaunchpadHandler simply adds the specified LFNs to JDL
| sndBox = 'InputSandbox = {"' + '","'.join(fileNameList + lfns) + '"};' |
JobWrapper simply passes the sandbox files with "LFN:" to DMS getFile
https://github.com/DIRACGrid/DIRAC/blob/fdfd3a4802a5543369d307cbbb3c0781f2f14219/src/DIRAC/WorkloadManagementSystem/JobWrapper/JobWrapper.py#L1127
Can there be some kind of protection to avoid this?
Preferably in JobLaunchpad, with the number of files, or with the total volume?
If that is difficult in the WebApp, then in JobWrapper where it can tell the disk space and the volume of the sandbox?
Metadata
Metadata
Assignees
Labels
No labels