redpanda-data / redpanda-data/connect
Retry Backoff configs not considered.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
The retry.backoff settings are not considered during the failures. The retries seem to be going off based on the default values.
The config is as below. Attaching the full config yaml.
label: "output_pubsub_fallback"
fallback:
- retry:
max_retries: 3
backoff:
initial_interval: 5s
max_interval: 50s
max_elapsed_time: 10m
output:
resource: output_pubsub
- broker:
pattern: fan_out_sequential
outputs:
- resource: log_kafka_msg_metadata_info
- resource: log_kafka_msg_content_debug
- resource: log_error
- resource: drop_to_dlq_kafka
benthos -e "./benthos-configs/env-files/q2/q2.env" -c benthos-configs/config.yaml
Version: 4.19.0
Date: 2023-08-17T19:31:04Z
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the provided retry configuration and the benthos -e ... -c ... command, then compare the observed retry timing with the configured backoff values. Trace the retry handling from the fallback output and verify that initial_interval, max_interval, and max_elapsed_time affect failures; done when the configured values are honored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100