You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    « Previous Version 9 Next »

     Click here for details...

    Flags
     List of submission flag strings (comma separated). Click 'Browse' to choose required job flags.

     

    Flag

    Value

    Description

    auto_mount

    		8

    Require automatic drive mounts on worker.

    auto_wrangling

    		16384

    Enable auto-wrangling for this job.

    convert_path131072Automatically convert paths on worker at runtime.

    disable_auto_complete

    		8192

    Normally instances are automatically completed by the system when a job runs out of available agenda items. Setting this flag disables that.

    disable_cpu_limit

    		4096

    Normally, if a job is submitted with the number of instances greater than there are agenda items, Qube! automatically shrinks the number of instances to be equal to the number of agenda items. Setting this flag disables that.

    disable_windows_job_object

    		2048

    (Deprecated in Qube6.5) Disable Windows' process management mechanism (called the "Job Object") that Qube! normally uses to manage job processes. Some applications already use it internally, and job objects don't nest well within other job objects, causing jobs to crash unexpectedly.

    elite

    		512

    Submit job as an elite job, which will be started immediately regardless of how busy the farm is. Elite jobs are also protected from preemption. Must be admin.

    export_environment

    		16

    Use environment variables set in the submission environment, when running the job on the workers.

    expand

    		32

    (Deprecated in Qube6.5) Automatically expand job to use as many instances as there are agenda items (limited by the total job slots in the farm).

    grid

    		4

    Wait for all instances to start before beginning work (useful for implementation of parallel jobs, such as satellite renders).

    host_list

    		256

    Run job on all candidate hosts, as filtered by other options (such as "hosts" or "groups").

    mail

    		1024

    Send e-mail when job is done.

    migrate_on_frame_retry

    		65536

    When an agenda item (frame) fails but is retried automatically because the retrywork option is set, setting this flag causes the instances to be migrated to another worker host, preventing the frame from running on the same host.

    no_defaults524288Prevent supervisor from applying supervisor_job_flags

    p_agenda

    		32768

    Enable p-agenda for this job, so that some frames are processed at a higher priority.

    uninterruptible

    		1

    Prevent job from being preempted.

     

    Dependency
    Wait for specified jobs to complete before starting this job (comma-separated). Click 'Add' to create dependent jobs.

    You can link jobs to each other in several ways:

    • "complete" means only start this job after designated job completes
    • "failed" means only start this job if the designated job fails
    • "killed" means only start this job if the designated job has been killed
    • "done" means start this job if the designated job is killed/failed/complete

    The second menu chooses between "job" (the entire set of frames) and "work" (typically a frame). So to link frame 1 of one job to frame 1 of a second, job, you would choose "work" in this menu. If you want to wait for all the frames of one job to complete before starting a second, then choose "job". The other option, "subjob", refers to the instance of a job. This is much less common, but means that, for example, the instance of Maya that was running frames has completed.


    Email (job complete)
    Send email on job completion (success or failure). Sends mail to the designated user.

    Email (failed frames)
    Sends mail to the designated user if frames fail.

    Blocked
    Set initial state of job to "blocked".

    Stderr->Stdout
    Redirect and consolidate the job stderr stream to the stdout stream. Enable this if you would like to combine your logs into one stream.

    Job Label
    Optional label to identify the job. Must be unique within a Job Process Group. This is most useful for submitting sets of dependent jobs, where you don't know in advance the job IDs to depend on, but you do know the labels. 

    Job Kind
    Arbitrary typing information that can be used to identify the job. It is commonly used to make sure only one of this "kind" of job runs on a worker at the same time by setting the job's requirements to include "not (job.kind in host.duty.kind)". See How to restrict a host to only one instance of a given kind of job, but still allow other jobs

    Process Group
    Job Process Group for logically organizing dependent jobs. Defaults to the jobid. Combination of "label" and "Process Group" must be unique for a job. See Process group labels

    Retry Frame/Instance
    Number of times to retry a failed frame/job instance. The default value of -1 means don't retry.

    Retry Work Delay
    Number of seconds between retries.

    Subjob Timeout
    Kill the subjob process if running for the specified time (in seconds).  Value of -1 means disabled. Use this if the acceptable instance/subjob spawn time is known.

    Frame Timeout
    Kill the agenda/frame if running for the specified time (in seconds).  Value of -1 means disabled. Use this if you know how long frames should take, so that you can automatically kill those running long.

    • No labels