[#398] Support retryer #398
No reviewers
TrueCloudLab/storage-services-committers
TrueCloudLab/storage-services-developers
Labels
No Label
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#398
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "dkirillov/frostfs-s3-gw:bugfix/retry_put_bucket_settings_on_creation"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Add two strategy for PutBucketSettings request retryer:
max_backoff
delays with jitter)max_backoff
delay between requests)Signed-off-by: Denis Kirillov d.kirillov@yadro.com
This PR is blocked by TrueCloudLab/frostfs-sdk-go#226
WIP: [#XX] Support retryerto WIP: [#398] Support retryerfe3452e170
to923ed520d4
923ed520d4
to707ee11d55
WIP: [#398] Support retryerto [#398] Support retryer@ -49,1 +49,4 @@
ACLEnabled() bool
RetryMaxAttempts() int
RetryMaxBackoff() time.Duration
RetryStrategy() RetryStrategy
What you think about grouping those retry variables in single
retryCfg
object`?Good idea. But then probably we need do the same for other parameters (placement policy related etc). Do we want such changes?
I didn't notice placement policy related parameters at first. Then it's okay to keep it for a while.
@ -66,0 +71,4 @@
const (
RetryStrategyExponential = "exponential"
RetryStrategyConstant = "constant"
)
Matter of taste, but do you consider keeping this in
pkg/retryer
?Hm... Is it ok that these constant won't be used in package when they are located? If it's ok then I'll move them
Agree, this is application level constants, there is no need to define it in package.
@ -10,3 +10,4 @@
git.frostfs.info/TrueCloudLab/policy-engine v0.0.0-20240527065402-303a81cdc6db
git.frostfs.info/TrueCloudLab/zapjournald v0.0.0-20240124114243-cb2e66427d02
github.com/aws/aws-sdk-go v1.44.6
github.com/aws/aws-sdk-go-v2 v1.18.1
Can we keep single
aws-sdk-go
dependency across all the code? I don't mind to ditch v1I would do this when branch https://git.frostfs.info/dkirillov/frostfs-s3-gw/commits/branch/feature/339-sigv4a_support be merged to master
707ee11d55
tocbf2bbae11