Submits jobs to the cluster’s Job Queue.
usage: awsbsub [-h] [-jn JOB_NAME] [-c CLUSTER] [-cf] [-p VCPUS] [-m MEMORY]
[-r RETRY_ATTEMPTS] [-t TIMEOUT] [-a ARRAY_SIZE]
[-d DEPENDS_ON]
[command] [arguments [arguments ...]]
command | The command to submit (it must be available on the compute instances) or the file name to be transferred (see –command-file option). Default: <open file ‘<stdin>’, mode ‘r’ at 0x7f39503a90c0> |
arguments | Arguments for the command or the command-file (optional). |
-jn, --job-name | |
The name of the job. The first character must be alphanumeric, and up to 128 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed | |
-c, --cluster | Cluster to use |
-cf, --command-file | |
Identifies that the command is a file to be transferred to the compute instances Default: False | |
-p, --vcpus | The number of vCPUs to reserve for the container. When used in conjunction with –nodes it identifies the number of vCPUs per node. Default is 1 Default: 1 |
-m, --memory | The hard limit (in MiB) of memory to present to the job. If your job attempts to exceed the memory specified here, the job is killed. Default is 128 Default: 128 |
-r, --retry-attempts | |
The number of times to move a job to the RUNNABLE status. You may specify between 1 and 10 attempts. If the value of attempts is greater than one, the job is retried if it fails until it has moved to RUNNABLE that many times. Default value is 1 Default: 1 | |
-t, --timeout | The time duration in seconds (measured from the job attempt’s startedAt timestamp) after which AWS Batch terminates your jobs if they have not finished. It must be at least 60 seconds |
-a, --array-size | |
The size of the array. It can be between 2 and 10,000. If you specify array properties for a job, it becomes an array job | |
-d, --depends-on | |
A semicolon separated list of dependencies for the job. A job can depend upon a maximum of 20 jobs. You can specify a SEQUENTIAL type dependency without specifying a job ID for array jobs so that each child array job completes sequentially, starting at index 0. You can also specify an N_TO_N type dependency with a job ID for array jobs so that each index child of this job must wait for the corresponding index child of each dependency to complete before it can begin. Syntax: jobId=<string>,type=<string>;… |