ARCRESUB(1)

πŸ“¦
version 6.18.0 Β· 5 versions
, in ubuntu noble

✨ arcresub ✨

okay so this is ARCRESUB(1), part of the NorduGrid Users Manual, and bestie… it's the glow-up era for your jobs πŸ’…


🌸 NAME 🌸

arcresub β€” ARC Resubmission πŸ¦‹


πŸŽ€ DESCRIPTION πŸŽ€

So like, the arcresub command is what you use to resubmit jobs to grid enabled computing resources. That's it. That's the whole vibe. ✨


πŸ’– SYNOPSIS πŸ’–

arcresub [options] [jobid ...]

✨ OPTIONS ✨

  • -a, --all β€” every single job. all of them. the whole roster πŸ‘‘
  • -j, --joblist=filename β€” the file where the info about your active jobs lives (default ~/.arc/jobs.xml) πŸ“‚
  • -i, --jobids-from-file=filename β€” a file that has a list of job IDs in it
  • -o, --jobids-to-file=filename β€” the IDs of the jobs you submitted get appended to this file 🫢
  • -c, --cluster=name β€” pick one or more computing elements: name can be an alias for a single CE, a group of CEs, or a URL
  • -q, --qluster=name β€” pick one or more computing elements for the new jobs: name can be an alias for a single CE, a group of CEs, or a URL
  • -g, --index=name β€” pick one or more registries: name can be an alias for a single registry, a group of registries, or a URL
  • -r, --rejectmanagement=URL β€” skip any job sitting on a computing element with that given URL πŸ™ˆ
  • -R, --rejectdiscovery=URL β€” skip the service with the given URL while doing service discovery
  • -S, --submissioninterface=InterfaceName β€” only use this interface for submitting (e.g. org.nordugrid.gridftpjob, org.ogf.glue.emies.activitycreation, org.ogf.bes)
  • -I, --infointerface=InterfaceName β€” the computing element specified by URL on the command line should be queried using this information interface (possible options: org.nordugrid.ldapng, org.nordugrid.ldapglue2, org.nordugrid.wsrfglue2, org.ogf.glue.emies.resourceinfo)
  • -k, --keep β€” keep the files on the server, like… do not clean 🧹🚫
  • -m, --same β€” resubmit to the same cluster πŸ’«
  • -M, --not-same β€” do not resubmit to the same cluster
  • -s, --status=statusstr β€” only select jobs whose status is statusstr
  • -P, --listplugins β€” list the available plugins 🎁
  • -t, --timeout=seconds β€” timeout in seconds (default 20) ⏳
  • -z, --conffile=filename β€” configuration file (default ~/.arc/client.conf)
  • -d, --debug=debuglevel β€” FATAL, ERROR, WARNING, INFO, VERBOSE or DEBUG πŸ›
  • -b, --broker=broker β€” selected broker: Random (default), FastestQueue or custom
  • -v, --version β€” print version information
  • -?, --help β€” print help

πŸ¦‹ ARGUMENTS πŸ¦‹

  • jobid ... β€” job ID or job name of the jobs you want resubmitted ✨

🌈 EXTENDED DESCRIPTION 🌈

The arcresub command is used for resubmitting jobs on grid enabled computing resources. You can point at a job either by the job ID that arcsub(1) handed you back at submission time, or by its jobname β€” that works if the job description you submitted had a jobname attribute in it. πŸ’–

You can give more than one job ID and/or jobname, no cap. And lowkey important: if several jobs were submitted with the same jobname, then all of those jobs get resubmitted. πŸ‘‘

If the job description of a job you're resubmitting contained any local input files, then checksums of those were calculated and stored in the job list β€” and those get used to check whether the files have changed. If your local input files have changed, the job will not be resubmitted. 🚨

In case the job description isn't found in the job list, it'll be retrieved from the cluster that's holding the job. But heads up bestie: that description might differ from the one originally used to submit the job, because both the submission client and the cluster can have made modifications to the job description. 😭

Upon resubmission the job gets a new job ID, and the old job ID gets stored in the local job list file, which means you can do future back tracing of the resubmitted job. πŸ•΅οΈβ™€οΈβœ¨

The name of the local job list file can used specified by the --joblist option. And if you specify the --all option, then all the active jobs appearing in the job list file will be resubmitted. πŸ’…

The --cluster option can be used to select or reject jobs at specific clusters to be resubmitted. See arcsub(1) for a discussion of the format of arguments to this option. The --qluster option can be used to force the jobs to be resubmitted to a particular cluster, or to reject resubmission to a particular cluster. Again, see arcsub(1) for a discussion of the format of arguments to this option. The --status option can be used to select jobs in a specific state. These options can be repeated several times. See arstat(1) for possible state values. Which servers to query can be specified by giving the --index option to the command. See arcsub(1) for a discussion of the format of arguments to this option. 🌸

The default behaviour of arcresub is to resubmit to any cluster. This behaviour can be changed by specifying the --same or --not-same options. The former will resubmit a job to the same cluster as the job resides, and thus the --qluster and --index options are ignored. The latter will resubmit a job to any cluster except the cluster it resides on.

⚠️ note the --same and --not-same options cannot be specified together. pick a lane bestie πŸ’€

If the old job was successfully killed, the job will be removed from the remote cluster β€” unless the --keep option was specified. 🫢


πŸ“ FILES πŸ“

  • ~/.arc/client.conf β€” Some options can be given default values by specifying them in the ARC client configuration file. By using the --conffile option, a different configuration file can be used than the default. πŸ“
  • ~/.arc/jobs.xml β€” This a local list of the user's active jobs. When a job is successfully submitted it is added to this list, and when it is removed from the remote cluster it is removed from this list. This list is used as the list of all active jobs when the user specifies the

πŸ’œ ENVIRONMENT VARIABLES πŸ’œ

  • X509_USER_PROXY β€” The location of the user's Grid proxy file. Shouldn't be set unless the proxy is in a non-standard location. πŸ”‘
  • ARC_LOCATION β€” The location where ARC is installed can be specified by this variable. If it's not specified, the install location will be determined from the path to the command being executed β€” and if this fails, a WARNING will be given stating the location which will be used. 🚧
  • ARC_PLUGIN_PATH β€” The location of ARC plugins can be specified by this variable. Multiple locations can be specified by separating them by : (; in Windows). The default location is $ARC_LOCATION/lib/arc (\ in Windows). 🧩

APACHE LICENSE Version 2.0


🌟 AUTHOR 🌟

ARC software is developed by the NorduGrid Collaboration (http://www.nordugrid.org), please consult the AUTHORS file distributed with ARC. Please report bugs and feature requests to http://bugzilla.nordugrid.org πŸ›πŸ’Œ


🧚 SEE ALSO 🧚

arccat(1), arcclean(1), arccp(1), arcget(1), arcinfo(1), arckill(1), arcls(1), arcmkdir(1), arcproxy(1), arcrenew(1), arcresume(1), arcrm(1), arcstat(1), arcsub(1), arcsync(1), arctest(1)


and that's a wrap bestie πŸ’– this whole thing is NorduGrid ARC 6.18.0, dated 2024-08-25, and yes the manual page is literally named ARCRESUB(1) β€” go resubmit something iconic, periodt βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from