Improve determining AccessBox
latest version #335
Labels
No labels
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 project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#335
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is your feature request related to a problem? Please describe.
Currently we can have multiple
AccessBox
version #135. To find out which version is last we sort them by creation epoch and object id but we don't take into accountS3-CRDT-Versions-Add
header. If we create several versions of credentials during the same epoch we cannot be sure that the last one we created be considered s3-gw as latest (though no split brain and we exactly know the actual order and it represented in headers)So I want the following test pass:
Describe the solution you'd like
Use
S3-CRDT-Versions-Add
header to know if one version is older than other (one version exists in header of other one). And only if neither one or second version id is contained in other headers use creation epoch and oid comparisonDescribe alternatives you've considered
Don't do anything
Additional context
No
Done in #391