Skip to content

EOS

This section covers known issues and recommendations related to EOS.

How to best access EOS from central services

The EOS team provides a KB with recommendations to best access EOS: KB0004244.

No EOS submission allowed

As of today, one should not place logs mentioned in the HTCondor submit file to EOS. This restriction may be lifted in future when a EOS fuse-bind library with a better performance becomes available.

In the meantime, please instruct your executable to stage-in from / stage-out to EOS, from within the executable script.

The following elements of the HTCondor submit file should not contain path pointing to EOS mount point (starting with /eos/):

  • executable
  • log
  • input
  • output
  • error
  • initialdir

Note

If you are unsure about what field is causing this error, you can use the -verbose flag to print all the details of your job: Example: condor_submit -verbose job.sub.

If either of these elements points to a file under /eos/, you will experience submission error ERROR: EOS Submission is not currently supported by the HTCondor Service.

There are several approaches available to avoid this error:

  • Use -spool option of condor_submit so that HTCondor asynchronously transfers data from its source to the schedd and then to the execution node. In this case, there is no shared file system involved and you will have to actively download the data with condor_transfer_data. For more information, please refer the Spool submission section of Data Flow.
$ condor_submit -spool hello.jdl

  • Use AFS for your log files: provide AFS paths that are writeable for your user instead of EOS paths.

  • Stage files in/out directly from EOS to the execution node or vice versa, without any restriction by using EOS commands (see Big files for an example) or the xrootd file transfer plugin.

Last update: December 18, 2024