DLQ
DLQ storage can be configured for certain errors thrown by sink.
DLQ_SINK_ENABLE
- Example value:
true
- Type:
optional
- Default value:
false
DLQ_WRITER_TYPE
DLQ Writer to be configured. The possible values are, KAFKA,BLOB_STORAGE,LOG
- Example value:
BLOB_STORAGE
- Type:
optional
- Default value:
LOG
DLQ_RETRY_MAX_ATTEMPTS
Max attempts to retry for dlq.
- Example value:
3
- Type:
optional
- Default value:
2147483647
DLQ_RETRY_FAIL_AFTER_MAX_ATTEMPT_ENABLE
- Example value:
true
- Type:
optional
- Default value:
false
DLQ_BLOB_STORAGE_TYPE
If the writer type is set to BLOB_STORAGE, we can choose any blob storage. Currently, GCS, S3, COS, and OSS are supported.
- Example value:
GCS
- Type:
optional
- Default value:
GCS
DLQ_BLOB_FILE_PARTITION_TIMEZONE
Timezone to be used for date-based partitioning of DLQ files when using BLOB_STORAGE writer type. DLQ files are organized into directories based on the consume timestamp of the message converted to the specified timezone. The configuration accepts standard timezone identifiers and will fail application startup if an invalid timezone is provided.
- Example value:
Asia/Tokyo
- Type:
optional
- Default value:
UTC
Valid Timezone Formats
1. IANA Timezone Identifiers
Handles daylight saving time transitions automatically.
- Example:
Asia/Jakarta
- Western Indonesia Time (UTC+7) - Format:
Continent/City
pattern (e.g.,America/New_York
,Europe/London
,Australia/Sydney
)
2. UTC Offset Formats
Fixed offset from UTC.
- Example:
+05:30
- 5 hours 30 minutes ahead of UTC - Format:
±HH:MM
orUTC±H
(e.g.,-08:00
,UTC+9
)
3. UTC Variants
- Example:
UTC
- Coordinated Universal Time - Supported:
UTC
,GMT
,Z
4. Legacy Timezone IDs
- Example:
JST
- Japan Standard Time - Supported:
EST
,PST
,JST
DLQ_GCS_GOOGLE_CLOUD_PROJECT_ID
- Example value:
my-project-id
- Type:
Required if BLOB storage type is GCS
DLQ_GCS_BUCKET_NAME
- Example value:
dlq-bucket
- Type:
Required if BLOB storage type is GCS
DLQ_GCS_CREDENTIAL_PATH
- Example value:
/path/for/json/credential
- Type:
Required if BLOB storage type is GCS
DLQ_GCS_RETRY_MAX_ATTEMPTS
- Example value:
3
- Type:
optional
- Default value:
10
DLQ_GCS_RETRY_TOTAL_TIMEOUT_MS
- Example value:
120000
- Type:
optional
- Default value:
120000
DLQ_GCS_RETRY_INITIAL_DELAY_MS
- Example value:
1000
- Type:
optional
- Default value:
1000
DLQ_GCS_RETRY_MAX_DELAY_MS
- Example value:
30000
- Type:
optional
- Default value:
30000
DLQ_GCS_RETRY_DELAY_MULTIPLIER
- Example value:
2
- Type:
optional
- Default value:
2
DLQ_GCS_RETRY_INITIAL_RPC_TIMEOUT_MS
- Example value:
5000
- Type:
optional
- Default value:
5000
DLQ_GCS_RETRY_RPC_TIMEOUT_MULTIPLIER
- Example value:
1
- Type:
optional
- Default value:
1
DLQ_GCS_RETRY_RPC_MAX_TIMEOUT_MS
- Example value:
5000
- Type:
optional
- Default value:
5000
DLQ_KAFKA_ACKS
- Example value:
all
- Type:
optional
- Default value:
all
DLQ_KAFKA_RETRIES
- Example value:
3
- Type:
optional
- Default value:
2147483647
DLQ_KAFKA_BATCH_SIZE
- Example value:
100
- Type:
optional
- Default value:
16384
DLQ_KAFKA_LINGER_MS
- Example value:
5
- Type:
optional
- Default value:
0
DLQ_KAFKA_BUFFER_MEMORY
- Example value:
33554432
- Type:
optional
- Default value:
33554432
DLQ_KAFKA_KEY_SERIALIZER
- Example value:
your.own.class
- Type:
optional
- Default value:
org.apache.kafka.common.serialization.ByteArraySerializer
DLQ_KAFKA_VALUE_SERIALIZER
- Example value:
your.own.class
- Type:
optional
- Default value:
org.apache.kafka.common.serialization.ByteArraySerializer
DLQ_KAFKA_BROKERS
- Example value:
127.0.0.1:1234
- Type:
required if writer type is kafka
DLQ_KAFKA_TOPIC
- Example value:
your-own-topic
- Type:
optional
- Default value:
firehose-retry-topic
DLQ_KAFKA_(.*)
- Example property:
DLQ_KAFKA_SASL_JAAS_CONFIG
,DLQ_KAFKA_SECURITY_PROTOCOL
,DLQ_KAFKA_SSL_TRUSTSTORE_PASSWORD
,DLQ_KAFKA_SASL_MECHANISM
- Type:
optional
- Default value:
null
- Description: Any property starting with
DLQ_KAFKA_
will be passed to the kafka producer. This one is useful for setting any kafka producer property that is not available in the configuration.
DLQ_S3_REGION"
Amazon S3 creates buckets in a Region that you specify.
- Example value:
ap-south-1
- Type:
required
DLQ_S3_BUCKET_NAME"
The Name of Amazon S3 bucket .Here is further documentation of s3 bucket name.
- Example value:
sink_bucket
- Type:
required
DLQ_S3_ACCESS_KEY"
Access Key to access the bucket. This key can also be set through env using AWS_ACCESS_KEY_ID
key or by creating credentials file in ${HOME}/.aws/credentials
folder . Here is further documentation on how to set through credentials file or environment varialbes
- Example value:
AKIAIOSFODNN7EXAMPLE
- Type:
required
DLQ_S3_SECRET_KEY"
Secret Key to access the bucket. This key can also be set through env using AWS_SECRET_ACCESS_KEY
key or by creating credentials file in ${HOME}/.aws/credentials
folder . Here is further documentation on how to set through credentials file or environment varialbes
- Example value:
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
- Type:
required
DLQ_S3_RETRY_MAX_ATTEMPTS
Number of retry of the s3 upload request when the request failed.
- Example value:
10
- Type:
optional
- Default value :
10
DLQ_S3_BASE_DELAY_MS"
Initial delay for first retry in milliseconds.
- Example value:
1000
- Type:
optional
- Default value :
1000
DLQ_S3_MAX_BACKOFF_MS"
Max backoff time for retry in milliseconds
- Example value:
30000
- Type:
optional
- Default value :
30000
DLQ_S3_API_ATTEMPT_TIMEOUT_MS"
The amount of time to wait for the http request to complete before giving up and timing out in milliseconds.
- Example value:
10000
- Type:
optional
- Default value :
10000
DLQ_S3_API_TIMEOUT_MS"
The amount of time to allow the client to complete the execution of an API call. This timeout covers the entire client execution except for marshalling. Unit is in milliseconds.
- Example value:
40000
- Type:
optional
- Default value :
40000
DLQ_OSS_ENDPOINT
The endpoint of the oss service. For more information, please refer to the oss documentation. Mandatory if DLQ_BLOB_STORAGE_TYPE is OSS.
- Example value:
oss-cn-hangzhou.aliyuncs.com
- Type:
Required if DLQ_BLOB_STORAGE_TYPE is OSS
- Default value :
null
DLQ_OSS_ACCESS_ID
The access key id of the oss service. For more information, please refer to the oss documentation.
- Example value:
youraccessid
- Type:
Required if DLQ_BLOB_STORAGE_TYPE is OSS
DLQ_OSS_ACCESS_KEY
The access key secret of the oss service. For more information, please refer to the oss documentation.
- Example value:
youraccesskey
- Type:
Required if DLQ_BLOB_STORAGE_TYPE is OSS
DLQ_OSS_BUCKET_NAME
The name of the oss bucket. Must adhere to the naming rules of oss. For more information, please refer to the oss documentation.
- Example value:
oss_bucket
- Type:
Required if DLQ_BLOB_STORAGE_TYPE is OSS
DLQ_OSS_DIRECTORY_PREFIX
The prefix of the directory in the oss bucket. For more information, please refer to the oss documentation.
- Example value:
oss_prefix
- Type:
optional
DLQ_OSS_SOCKET_TIMEOUT_MS
The socket timeout in milliseconds.
- Example value:
10000
- Type:
required
- Default value :
50000
DLQ_OSS_CONNECTION_TIMEOUT_MS
The connection timeout in milliseconds.
- Example value:
50000
- Type:
required
- Default value :
50000
DLQ_OSS_CONNECTION_REQUEST_TIMEOUT_MS
The connection request timeout in milliseconds. Negative value indicates no timeout.
- Example value:
100
- Type:
required
- Default value :
-1
DLQ_OSS_REQUEST_TIMEOUT_MS
The request timeout in milliseconds.
- Example value:
50000
- Type:
required
- Default value :
300000
DLQ_OSS_RETRY_ENABLED
The flag to enable retry mechanism for OSS client when transient failure occurred.
- Example value:
true
- Type:
required
- Default value :
true
DLQ_OSS_MAX_RETRY_ATTEMPTS
The maximum number of retry attempts. To be used in conjunction when DLQ_OSS_RETRY_ENABLED
is set to true
.
- Example value:
3
- Type:
required
- Default value :
3
DLQ_COS_REGION
The region where your Tencent COS bucket is located. For example, 'ap-beijing', 'ap-guangzhou'. For a complete list of regions, refer to Tencent COS Regions and Access Endpoints.
- Example value:
ap-beijing
- Type:
Required if DLQ_BLOB_STORAGE_TYPE is COS
DLQ_COS_BUCKET_NAME
The name of your Tencent COS bucket. Must follow COS bucket naming conventions: lowercase letters, numbers, and hyphens (-), 1-40 characters.
- Example value:
my-dlq-bucket
- Type:
Required if DLQ_BLOB_STORAGE_TYPE is COS
DLQ_COS_DIRECTORY_PREFIX
Optional prefix for organizing objects within the bucket. Acts like a folder path. Will be prepended to all object keys.
- Example value:
dlq/failed-messages/
- Type:
optional
- Default value:
""
DLQ_COS_SECRET_ID
The SecretId part of your Tencent Cloud API credentials. Can be obtained from the Tencent Cloud Console.
- Example value:
your-secret-id-here
- Type:
Required if DLQ_BLOB_STORAGE_TYPE is COS
DLQ_COS_SECRET_KEY
The SecretKey part of your Tencent Cloud API credentials. Can be obtained from the Tencent Cloud Console.
- Example value:
your-secret-key-here
- Type:
Required if DLQ_BLOB_STORAGE_TYPE is COS
DLQ_COS_TEMP_CREDENTIAL_VALIDITY_SECONDS
Duration in seconds for which temporary credentials are valid when using STS (Security Token Service). These temporary credentials are automatically refreshed before expiration.
- Example value:
1800
- Type:
optional
- Default value:
1800
(30 minutes)
DLQ_COS_APPID
Your Tencent Cloud Account's APPID. Can be found in the Tencent Cloud Console.
- Example value:
1250000000
- Type:
Required if DLQ_BLOB_STORAGE_TYPE is COS
DLQ_COS_RETRY_MAX_ATTEMPTS
Maximum number of retry attempts for failed COS operations before giving up.
- Example value:
10
- Type:
optional
- Default value:
10
DLQ_COS_RETRY_INITIAL_DELAY_MS
Initial delay in milliseconds before the first retry attempt. For subsequent retries, this value may be increased based on retry strategy.
- Example value:
1000
- Type:
optional
- Default value:
1000
(1 second)
DLQ_COS_RETRY_MAX_DELAY_MS
Maximum delay in milliseconds between retry attempts. The actual delay will not exceed this value, even with exponential backoff.
- Example value:
30000
- Type:
optional
- Default value:
30000
(30 seconds)
DLQ_COS_RETRY_TOTAL_TIMEOUT_MS
Total timeout in milliseconds for all retry attempts combined. If exceeded, no more retries will be attempted.
- Example value:
120000
- Type:
optional
- Default value:
120000
(2 minutes)
DLQ_COS_CONNECTION_TIMEOUT_MS
Timeout in milliseconds for establishing a connection to COS.
- Example value:
5000
- Type:
optional
- Default value:
5000
(5 seconds)
DLQ_COS_SOCKET_TIMEOUT_MS
Timeout in milliseconds for waiting for data from an established connection to COS.
- Example value:
50000
- Type:
optional
- Default value:
50000
(50 seconds)
DLQ_COS_RETRY_DELAY_MS
Base delay in milliseconds between retry attempts. This value may be increased for subsequent retries based on retry strategy.
- Example value:
1000
- Type:
optional
- Default value:
1000
(1 second)