Skip to content

SchedulerConfiguration

Used by
Source code in docs_src/capo_emr_containers/types/scheduler_configuration.py 
12
13
14
15
16
17
18
19
20
class SchedulerConfiguration(TypedDict, closed=True):
    max_in_queue_job_runs: NotRequired[
        "capo_emr_containers.types.in_queue_job_limit_integer.InQueueJobLimitInteger"
    ]
    """<p>The maximum number of job runs that can be in the <code>PENDING</code> or <code>SUBMITTED</code> state at any time for the virtual cluster. When the queue is full, the service rejects <code>StartJobRun</code> requests with a <code>ValidationException</code>. If you omit this field, the service applies no queue-depth limit.</p>"""
    max_concurrent_job_runs: NotRequired[
        "capo_emr_containers.types.job_limit_integer.JobLimitInteger"
    ]
    """<p>The maximum number of job runs that can be in the <code>RUNNING</code> state at any time for the virtual cluster. As running slots free up, queued job runs start automatically. If you omit this field, the service applies no concurrency limit.</p>"""

max_concurrent_job_runs instance-attribute 

max_concurrent_job_runs: NotRequired[JobLimitInteger]

The maximum number of job runs that can be in the RUNNING state at any time for the virtual cluster. As running slots free up, queued job runs start automatically. If you omit this field, the service applies no concurrency limit.

max_in_queue_job_runs instance-attribute 

max_in_queue_job_runs: NotRequired[InQueueJobLimitInteger]

The maximum number of job runs that can be in the PENDING or SUBMITTED state at any time for the virtual cluster. When the queue is full, the service rejects StartJobRun requests with a ValidationException. If you omit this field, the service applies no queue-depth limit.