Use SelectorAwaiting in case of read and delete load in s3_dar.js scenario #150
No reviewers
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/xk6-frostfs#150
Loading…
Reference in a new issue
No description provided.
Delete branch "mmalygina/xk6-frostfs:investigate-deletes"
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?
Use SelectorAwaiting in case of read and delete load in s3_dar.js scenario
Signed-off-by: m.malygina m.malygina@yadro.com
@ -76,3 +87,3 @@
let obj_to_delete_exit_on_null = undefined;
if (registry_enabled && delete_age) {
obj_to_delete_exit_on_null = write_vu_count == 0;
obj_to_delete_exit_on_null = (write_vu_count == 0) && (read_vu_count == 0)
How does it help?
In case we are running both read and delete load we don't use SelectorOneshot, but use SelectorAwaiting
c7fd2078c8
to0a9aeab47c
Please, rephrase the commit message, it should start with a verb in imperative (like use). Your PR title is OK to be used as the commit message.
[#150] scenarios: Use SelectorAwaiting for read and delete load in s3_dar.js