[#99] Adding read age param to improve k6 runs stability #99
No reviewers
TrueCloudLab/storage-core-committers
TrueCloudLab/storage-core-developers
TrueCloudLab/storage-services-committers
TrueCloudLab/storage-services-developers
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 milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/xk6-frostfs#99
Loading…
Reference in a new issue
No description provided.
Delete branch "abereziny/xk6-frostfs:feature-add-read-age"
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?
Since #86 we are now reading from registry, but most of the time cluster needs some time before all nodes are aware about objects.
So adding customizable read_age for obj_to_read_selector
Internal sanity checks showed that errors count got down to 0% in basic scenarios
Signed-off-by: Andrey Berezin a.berezin@yadro.com
d372e52ea5
to1311051f60