Use SelectorAwaiting in case of read and delete load in s3_dar.js scenario #150

Merged
fyrchik merged 2 commits from mmalygina/xk6-frostfs:investigate-deletes into master 2024-06-21 13:03:57 +00:00
Collaborator

Use SelectorAwaiting in case of read and delete load in s3_dar.js scenario

Signed-off-by: m.malygina m.malygina@yadro.com

Use SelectorAwaiting in case of read and delete load in s3_dar.js scenario Signed-off-by: m.malygina <m.malygina@yadro.com>
mmalygina added 1 commit 2024-06-20 14:05:13 +00:00
DCO action / DCO (pull_request) Failing after 3m9s Details
Tests and linters / Tests (1.21) (pull_request) Successful in 5m13s Details
Tests and linters / Tests with -race (pull_request) Successful in 5m11s Details
Tests and linters / Tests (1.22) (pull_request) Successful in 5m34s Details
Tests and linters / Lint (pull_request) Successful in 3m20s Details
0b50950974
use getSelector in case of read and delete load
Signed-off-by: m.malygina <m.malygina@yadro.com>
dstepanov-yadro approved these changes 2024-06-20 14:25:58 +00:00
fyrchik reviewed 2024-06-20 16:35:08 +00:00
@ -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?

How does it help?
Poster
Collaborator

In case we are running both read and delete load we don't use SelectorOneshot, but use SelectorAwaiting

In case we are running both read and delete load we don't use SelectorOneshot, but use SelectorAwaiting
mmalygina added 1 commit 2024-06-21 07:55:06 +00:00
Tests and linters / Tests (1.22) (pull_request) Failing after 18s Details
DCO action / DCO (pull_request) Failing after 1m45s Details
Tests and linters / Tests (1.21) (pull_request) Successful in 5m4s Details
Tests and linters / Tests with -race (pull_request) Successful in 5m21s Details
Tests and linters / Lint (pull_request) Successful in 6m3s Details
c7fd2078c8
[#150] In case we are running both read and delete load SelectorAwaiting
Signed-off-by: m.malygina <m.malygina@yadro.com>
mmalygina force-pushed investigate-deletes from c7fd2078c8 to 0a9aeab47c 2024-06-21 07:55:56 +00:00 Compare
acid-ant approved these changes 2024-06-21 08:02:26 +00:00
dstepanov-yadro approved these changes 2024-06-21 08:15:42 +00:00

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

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`
mmalygina added 1 commit 2024-06-21 12:55:22 +00:00
DCO action / DCO (pull_request) Successful in 1m28s Details
Tests and linters / Tests (1.22) (pull_request) Successful in 3m14s Details
Tests and linters / Tests with -race (pull_request) Successful in 3m27s Details
Tests and linters / Tests (1.21) (pull_request) Successful in 3m40s Details
Tests and linters / Lint (pull_request) Successful in 4m29s Details
e7d4dd404a
[#150] scenarios: Use SelectorAwaiting for read and delete load in s3_dar.js, make delete_age optional
Signed-off-by: m.malygina <m.malygina@yadro.com>
fyrchik merged commit e7d4dd404a into master 2024-06-21 13:03:56 +00:00
Sign in to join this conversation.
There is no content yet.