opensearch-project / opensearch-project/data-prepper
Make maximum back-off delay a configuration option
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
At present the maximum back-off delay (for SQS, not sure if others) is hard coded, we would like to be able to set that to a user defined value
Describe the solution you'd like
A configuration option to set the maximum back-off delay
Describe alternatives you've considered (Optional)
Additional context
Sourced from https://github.com/opensearch-project/data-prepper/discussions/3726
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 locating the hard-coded maximum back-off delay in the SQS implementation and tracing how related settings are configured. Check the existing tests for back-off behavior and configuration; done means users can set the maximum delay and the configured value is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100