Hi,
I came across another issue while configuring our Tier3 cluster. (For now I’m just connecting to the cluster as user “xrootd”.)
The PROOF master needs to access the worker directories of the workers. Usually this is accomplished by adding something as simple as
all.export /home/proof r/w
or something similar to the configuration file. But the issue for us is a bit more tricky. We use xrootd separately from the PROOF cluster to manage the disk space on the cluster. Actually each worker has two cache directories which are mapped to the “/atlas” directory with something like:
set osscachepath = /local/xrootd
oss.space public $(osscachepath)/* xa
oss.usage log /var/log/xrootd
I’ve found that with oss running, I can’t just simply export a “real” local directory. Adding the all.export line to the configuration file controlling our XRootD storage system doesn’t make the servers export their local work area.
So I thought, okay, let’s just serve the work areas using the xrootd instance running PROOF. So I added this piece of configuration to my configuration file that I use to configure the PROOF cluster:
xrootd.fslib /export/share/atlas/root/proof/x86_64-slc5-gcc41-opt/lib/libXrdOfs.so
xrd.port 11094
all.export /local/home/proof r/w
However, even if I define my workers in the configuration file like this:
slave wrk0prv.physics.nyu.edu workdir=root://wrk0prv.physics.nyu.edu:11094//local/home/proof
The PROOF master still tries to read the output ROOT files at the end of the job using the default 1094 port:
So my question is twofold:
-
Is it possible to export a “regular” directory with XRootD when another “virtual” directory is configured using OSS?
-
If not, then can I force PROOF to connect to the files created by the workers using a specific port?
Either approach would be fine for me.
Attila