Reference documentation and code samples for the Google Cloud Tasks V2 Client class Queue.
A queue is a container of related tasks. Queues are configured to manage how those tasks are dispatched. Configurable properties include rate limits, retry options, queue types, and others.
Generated from protobuf message google.cloud.tasks.v2.Queue
Namespace
Google \ Cloud \ Tasks \ V2Methods
__construct
Constructor.
Parameters | |
---|---|
Name | Description |
data |
array
Optional. Data for populating the Message object. |
↳ name |
string
Caller-specified and required in CreateQueue, after which it becomes output only. The queue name. The queue name must have the following format: |
↳ app_engine_routing_override |
AppEngineRouting
Overrides for task-level app_engine_routing. These settings apply only to App Engine tasks in this queue. Http tasks are not affected. If set, |
↳ rate_limits |
RateLimits
Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts. However they control task attempts in different ways: * * rate_limits controls the total rate of dispatches from a queue (i.e. all traffic dispatched from the queue, regardless of whether the dispatch is from a first attempt or a retry). * * retry_config controls what happens to particular a task after its first attempt fails. That is, retry_config controls task retries (the second attempt, third attempt, etc). The queue's actual dispatch rate is the result of: * * Number of tasks in the queue * * User-specified throttling: rate_limits, retry_config, and the queue's state. * * System throttling due to |
↳ retry_config |
RetryConfig
Settings that determine the retry behavior. * * For tasks created using Cloud Tasks: the queue-level retry settings apply to all tasks in the queue that were created using Cloud Tasks. Retry settings cannot be set on individual tasks. * * For tasks created using the App Engine SDK: the queue-level retry settings apply to all tasks in the queue which do not have retry settings explicitly set on the task and were created by the App Engine SDK. See App Engine documentation. |
↳ state |
int
Output only. The state of the queue. |
↳ purge_time |
Google\Protobuf\Timestamp
Output only. The last time this queue was purged. All tasks that were created before this time were purged. A queue can be purged using PurgeQueue, the App Engine Task Queue SDK, or the Cloud Console. Purge time will be truncated to the nearest microsecond. Purge time will be unset if the queue has never been purged. |
↳ stackdriver_logging_config |
StackdriverLoggingConfig
Configuration options for writing logs to Stackdriver Logging. If this field is unset, then no logs are written. |
getName
Caller-specified and required in CreateQueue, after which it becomes output only.
The queue name.
The queue name must have the following format:
projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID
PROJECT_ID
can contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projectsLOCATION_ID
is the canonical ID for the queue's location. The list of available locations can be obtained by calling ListLocations. For more information, see https://cloud.google.com/about/locations/.QUEUE_ID
can contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters.
Returns | |
---|---|
Type | Description |
string |
setName
Caller-specified and required in CreateQueue, after which it becomes output only.
The queue name.
The queue name must have the following format:
projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID
PROJECT_ID
can contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projectsLOCATION_ID
is the canonical ID for the queue's location. The list of available locations can be obtained by calling ListLocations. For more information, see https://cloud.google.com/about/locations/.QUEUE_ID
can contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters.
Parameter | |
---|---|
Name | Description |
var |
string
|
Returns | |
---|---|
Type | Description |
$this |
getAppEngineRoutingOverride
Overrides for task-level app_engine_routing.
These settings apply only to
App Engine tasks in this
queue. Http tasks are not affected.
If set, app_engine_routing_override
is used for all
App Engine tasks in the
queue, no matter what the setting is for the task-level
app_engine_routing.
Returns | |
---|---|
Type | Description |
AppEngineRouting|null |
hasAppEngineRoutingOverride
clearAppEngineRoutingOverride
setAppEngineRoutingOverride
Overrides for task-level app_engine_routing.
These settings apply only to
App Engine tasks in this
queue. Http tasks are not affected.
If set, app_engine_routing_override
is used for all
App Engine tasks in the
queue, no matter what the setting is for the task-level
app_engine_routing.
Parameter | |
---|---|
Name | Description |
var |
AppEngineRouting
|
Returns | |
---|---|
Type | Description |
$this |
getRateLimits
Rate limits for task dispatches.
rate_limits and retry_config are related because they both control task attempts. However they control task attempts in different ways:
- rate_limits controls the total rate of dispatches from a queue (i.e. all traffic dispatched from the queue, regardless of whether the dispatch is from a first attempt or a retry).
- retry_config controls what happens to particular a task after its first attempt fails. That is, retry_config controls task retries (the second attempt, third attempt, etc). The queue's actual dispatch rate is the result of:
- Number of tasks in the queue
- User-specified throttling: rate_limits, retry_config, and the queue's state.
- System throttling due to
429
(Too Many Requests) or503
(Service Unavailable) responses from the worker, high error rates, or to smooth sudden large traffic spikes.
Returns | |
---|---|
Type | Description |
RateLimits|null |
hasRateLimits
clearRateLimits
setRateLimits
Rate limits for task dispatches.
rate_limits and retry_config are related because they both control task attempts. However they control task attempts in different ways:
- rate_limits controls the total rate of dispatches from a queue (i.e. all traffic dispatched from the queue, regardless of whether the dispatch is from a first attempt or a retry).
- retry_config controls what happens to particular a task after its first attempt fails. That is, retry_config controls task retries (the second attempt, third attempt, etc). The queue's actual dispatch rate is the result of:
- Number of tasks in the queue
- User-specified throttling: rate_limits, retry_config, and the queue's state.
- System throttling due to
429
(Too Many Requests) or503
(Service Unavailable) responses from the worker, high error rates, or to smooth sudden large traffic spikes.
Parameter | |
---|---|
Name | Description |
var |
RateLimits
|
Returns | |
---|---|
Type | Description |
$this |
getRetryConfig
Settings that determine the retry behavior.
- For tasks created using Cloud Tasks: the queue-level retry settings apply to all tasks in the queue that were created using Cloud Tasks. Retry settings cannot be set on individual tasks.
- For tasks created using the App Engine SDK: the queue-level retry settings apply to all tasks in the queue which do not have retry settings explicitly set on the task and were created by the App Engine SDK. See App Engine documentation.
Returns | |
---|---|
Type | Description |
RetryConfig|null |
hasRetryConfig
clearRetryConfig
setRetryConfig
Settings that determine the retry behavior.
- For tasks created using Cloud Tasks: the queue-level retry settings apply to all tasks in the queue that were created using Cloud Tasks. Retry settings cannot be set on individual tasks.
- For tasks created using the App Engine SDK: the queue-level retry settings apply to all tasks in the queue which do not have retry settings explicitly set on the task and were created by the App Engine SDK. See App Engine documentation.
Parameter | |
---|---|
Name | Description |
var |
RetryConfig
|
Returns | |
---|---|
Type | Description |
$this |
getState
Output only. The state of the queue.
state
can only be changed by calling
PauseQueue,
ResumeQueue, or uploading
queue.yaml/xml.
UpdateQueue cannot be used
to change state
.
Returns | |
---|---|
Type | Description |
int |
setState
Output only. The state of the queue.
state
can only be changed by calling
PauseQueue,
ResumeQueue, or uploading
queue.yaml/xml.
UpdateQueue cannot be used
to change state
.
Parameter | |
---|---|
Name | Description |
var |
int
|
Returns | |
---|---|
Type | Description |
$this |
getPurgeTime
Output only. The last time this queue was purged.
All tasks that were created before this time were purged. A queue can be purged using PurgeQueue, the App Engine Task Queue SDK, or the Cloud Console. Purge time will be truncated to the nearest microsecond. Purge time will be unset if the queue has never been purged.
Returns | |
---|---|
Type | Description |
Google\Protobuf\Timestamp|null |
hasPurgeTime
clearPurgeTime
setPurgeTime
Output only. The last time this queue was purged.
All tasks that were created before this time were purged. A queue can be purged using PurgeQueue, the App Engine Task Queue SDK, or the Cloud Console. Purge time will be truncated to the nearest microsecond. Purge time will be unset if the queue has never been purged.
Parameter | |
---|---|
Name | Description |
var |
Google\Protobuf\Timestamp
|
Returns | |
---|---|
Type | Description |
$this |
getStackdriverLoggingConfig
Configuration options for writing logs to Stackdriver Logging. If this field is unset, then no logs are written.
Returns | |
---|---|
Type | Description |
StackdriverLoggingConfig|null |
hasStackdriverLoggingConfig
clearStackdriverLoggingConfig
setStackdriverLoggingConfig
Configuration options for writing logs to Stackdriver Logging. If this field is unset, then no logs are written.
Parameter | |
---|---|
Name | Description |
var |
StackdriverLoggingConfig
|
Returns | |
---|---|
Type | Description |
$this |