nspcc-dev/neofs-node

Fork 0

mirror of https://github.com/nspcc-dev/neofs-node.git synced 2026-03-01 04:29:10 +00:00

s3 PUT errors on AZ when we rebooted VEDI. #885

New issue

Closed

opened 2025-12-28 17:21:01 +00:00 by sami · 7 comments

sami commented

2025-12-28 17:21:01 +00:00

Owner

Originally created by @anikeev-yadro on GitHub (Nov 14, 2022).

Originally assigned to: @anikeev-yadro on GitHub.

Expected Behavior

We expect that reboot of one node not affected s3 load on other nodes.

Steps to Reproduce (for bugs)

1.Create s3 buckets and load objects with policy "node-off": "REP 2 CBF 2 SELECT 2 FROM *"

./scenarios/preset/preset_s3.py --size 64 --buckets 5 --out s3_64kb.json --endpoint 172.26.161.171:8084 --preload_obj 20 --location node-off

2.Start k6 R/W load on node AZ

admin@perf-load-01:~/xk6.new$ date;./k6 run -e DURATION=120 -e WRITERS=10 -e READERS=10 -e DELETERS=0 -e DELETE_AGE=10 -e REGISTRY_FILE=/tmp/s3_reg1411_01 -e WRITE_OBJ_SIZE=10000  -e S3_ENDPOINTS=172.26.161.171:8084 -e PREGEN_JSON=./../s3_64kb.json scenarios/s3.js
Пн 14 ноя 2022 14:59:32 UTC

3.Reboot node VEDI
4.Have a lot of PUT errors in k6:


          /\      |‾‾| /‾‾/   /‾‾/
     /\  /  \     |  |/  /   /  /
    /  \/    \    |     (   /   ‾‾\
   /          \   |  |\  \ |  (‾)  |
  / __________ \  |__| \__\ \_____/ .io

  execution: local
     script: scenarios/s3.js
     output: -

  scenarios: (100.00%) 2 scenarios, 20 max VUs, 2m5s max duration (incl. graceful stop):
           * read: 10 looping VUs for 2m0s (exec: obj_read, gracefulStop: 5s)
           * write: 10 looping VUs for 2m0s (exec: obj_write, gracefulStop: 5s)

INFO[0000] Pregenerated buckets:          5              source=console
INFO[0000] Pregenerated read object size: 64 Kb          source=console
INFO[0000] Pregenerated total objects:    100            source=console
INFO[0000] Reading VUs:                   10             source=console
INFO[0000] Writing VUs:                   10             source=console
INFO[0000] Deleting VUs:                  0              source=console
INFO[0000] Total VUs:                     20             source=console
INFO[0034] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 3b57c1a4-ddab-4a65-932a-68ff1619eed5, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0035] operation error S3: PutObject, https response error StatusCode: 500, RequestID: a6f1822b-7407-4136-b487-3023c7f6766f, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0035] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 38a269ac-87ee-412f-99b7-496c6cf128b3, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0035] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 9c0b2702-799d-41dd-96c4-d97297e13a4e, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0036] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 115ed1ee-f116-4bdd-8352-050f340280c8, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0036] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 7ed72b72-cfdc-4f8d-9096-ffd166b77340, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0037] operation error S3: PutObject, https response error StatusCode: 500, RequestID: e7ac27ac-548d-4bef-b811-ab6d008811b0, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0037] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 08f38672-7548-4657-9495-3110a44ec2b2, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0038] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 171e7640-b7b8-41b0-9162-8d1562f03873, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0040] operation error S3: PutObject, https response error StatusCode: 500, RequestID: c82db566-bd2a-42cf-a0e7-2edc666f920d, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0045] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 1588f25e-3250-44b9-b1e4-c3599d8e0b8c, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0045] operation error S3: PutObject, https response error StatusCode: 500, RequestID: a9b07587-955b-4cd9-b47e-6999009c6057, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0046] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 3d6728f8-1b85-44b0-9562-4e25d00ed914, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0047] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 8d7c7a67-4b01-45af-9e9b-db6d9b18d97f, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0048] operation error S3: PutObject, https response error StatusCode: 500, RequestID: d679e136-89a2-491c-b3ff-e2f8051d418c, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0049] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 5c3fc70c-14ce-4132-a0ed-81833b3a343b, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0049] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 1914da78-0b65-4c6f-8f12-6ef332e810ac, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console
INFO[0050] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 47169ed1-47c6-4b26-8660-4a42d752e812, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again.  source=console

running (2m02.7s), 00/20 VUs, 5733 complete and 0 interrupted iterations
read  ✓ [======================================] 10 VUs  2m0s
write ✓ [======================================] 10 VUs  2m0s

     █ setup

     █ teardown

     aws_obj_get_duration...: avg=216.07ms min=4.61ms   med=150.44ms max=10.24s p(90)=263.22ms p(95)=319.22ms
     aws_obj_get_total......: 5555   45.262652/s
     aws_obj_put_duration...: avg=6.21s    min=579.54ms med=6.8s     max=10.14s p(90)=7.58s    p(95)=7.76s
     aws_obj_put_fails......: 18     0.146666/s
     aws_obj_put_total......: 178    1.45036/s
     data_received..........: 363 MB 3.0 MB/s
     data_sent..............: 1.6 GB 13 MB/s
     iteration_duration.....: avg=421.28ms min=50.27µs  med=153.2ms  max=14.78s p(90)=287.1ms  p(95)=429.2ms
     iterations.............: 5733   46.713013/s
     vus....................: 5      min=5       max=20
     vus_max................: 20     min=20      max=20

As result PUT fails on 18 objects, which were not putted.

Logs and preload files: TEMP.zip
Version:

NeoFS Storage node
Version: v0.34.0-40-gcdbfd057
GoVersion: go1.18.4

Your Environment

Server setup and configuration:
cloud, 4 VMs, 4 SN, 4 http qw, 4 s3 gw

Operating System and version (uname -a):
linux vedi 5.10.0-16-amd64 https://github.com/nspcc-dev/neofs-node/issues/1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux

Originally created by @anikeev-yadro on GitHub (Nov 14, 2022). Originally assigned to: @anikeev-yadro on GitHub. ## Expected Behavior We expect that reboot of one node not affected s3 load on other nodes. ## Steps to Reproduce (for bugs) 1.Create s3 buckets and load objects with policy "node-off": "REP 2 CBF 2 SELECT 2 FROM *" ``` ./scenarios/preset/preset_s3.py --size 64 --buckets 5 --out s3_64kb.json --endpoint 172.26.161.171:8084 --preload_obj 20 --location node-off ``` 2.Start k6 R/W load on node AZ ``` admin@perf-load-01:~/xk6.new$ date;./k6 run -e DURATION=120 -e WRITERS=10 -e READERS=10 -e DELETERS=0 -e DELETE_AGE=10 -e REGISTRY_FILE=/tmp/s3_reg1411_01 -e WRITE_OBJ_SIZE=10000 -e S3_ENDPOINTS=172.26.161.171:8084 -e PREGEN_JSON=./../s3_64kb.json scenarios/s3.js Пн 14 ноя 2022 14:59:32 UTC ``` 3.Reboot node VEDI 4.Have a lot of PUT errors in k6: ``` /\ |‾‾| /‾‾/ /‾‾/ /\ / \ | |/ / / / / \/ \ | ( / ‾‾\ / \ | |\ \ | (‾) | / __________ \ |__| \__\ \_____/ .io execution: local script: scenarios/s3.js output: - scenarios: (100.00%) 2 scenarios, 20 max VUs, 2m5s max duration (incl. graceful stop): * read: 10 looping VUs for 2m0s (exec: obj_read, gracefulStop: 5s) * write: 10 looping VUs for 2m0s (exec: obj_write, gracefulStop: 5s) INFO[0000] Pregenerated buckets: 5 source=console INFO[0000] Pregenerated read object size: 64 Kb source=console INFO[0000] Pregenerated total objects: 100 source=console INFO[0000] Reading VUs: 10 source=console INFO[0000] Writing VUs: 10 source=console INFO[0000] Deleting VUs: 0 source=console INFO[0000] Total VUs: 20 source=console INFO[0034] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 3b57c1a4-ddab-4a65-932a-68ff1619eed5, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0035] operation error S3: PutObject, https response error StatusCode: 500, RequestID: a6f1822b-7407-4136-b487-3023c7f6766f, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0035] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 38a269ac-87ee-412f-99b7-496c6cf128b3, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0035] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 9c0b2702-799d-41dd-96c4-d97297e13a4e, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0036] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 115ed1ee-f116-4bdd-8352-050f340280c8, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0036] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 7ed72b72-cfdc-4f8d-9096-ffd166b77340, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0037] operation error S3: PutObject, https response error StatusCode: 500, RequestID: e7ac27ac-548d-4bef-b811-ab6d008811b0, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0037] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 08f38672-7548-4657-9495-3110a44ec2b2, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0038] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 171e7640-b7b8-41b0-9162-8d1562f03873, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0040] operation error S3: PutObject, https response error StatusCode: 500, RequestID: c82db566-bd2a-42cf-a0e7-2edc666f920d, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0045] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 1588f25e-3250-44b9-b1e4-c3599d8e0b8c, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0045] operation error S3: PutObject, https response error StatusCode: 500, RequestID: a9b07587-955b-4cd9-b47e-6999009c6057, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0046] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 3d6728f8-1b85-44b0-9562-4e25d00ed914, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0047] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 8d7c7a67-4b01-45af-9e9b-db6d9b18d97f, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0048] operation error S3: PutObject, https response error StatusCode: 500, RequestID: d679e136-89a2-491c-b3ff-e2f8051d418c, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0049] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 5c3fc70c-14ce-4132-a0ed-81833b3a343b, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0049] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 1914da78-0b65-4c6f-8f12-6ef332e810ac, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console INFO[0050] operation error S3: PutObject, https response error StatusCode: 500, RequestID: 47169ed1-47c6-4b26-8660-4a42d752e812, HostID: 21859b78-a8cb-4b31-bf6c-22eb3c585f8f, api error InternalError: We encountered an internal error, please try again. source=console running (2m02.7s), 00/20 VUs, 5733 complete and 0 interrupted iterations read ✓ [======================================] 10 VUs 2m0s write ✓ [======================================] 10 VUs 2m0s █ setup █ teardown aws_obj_get_duration...: avg=216.07ms min=4.61ms med=150.44ms max=10.24s p(90)=263.22ms p(95)=319.22ms aws_obj_get_total......: 5555 45.262652/s aws_obj_put_duration...: avg=6.21s min=579.54ms med=6.8s max=10.14s p(90)=7.58s p(95)=7.76s aws_obj_put_fails......: 18 0.146666/s aws_obj_put_total......: 178 1.45036/s data_received..........: 363 MB 3.0 MB/s data_sent..............: 1.6 GB 13 MB/s iteration_duration.....: avg=421.28ms min=50.27µs med=153.2ms max=14.78s p(90)=287.1ms p(95)=429.2ms iterations.............: 5733 46.713013/s vus....................: 5 min=5 max=20 vus_max................: 20 min=20 max=20 ``` As result PUT fails on 18 objects, which were not putted. **Logs and preload files:** [TEMP.zip](https://github.com/nspcc-dev/neofs-node/files/10004579/TEMP.zip) **Version:** ``` NeoFS Storage node Version: v0.34.0-40-gcdbfd057 GoVersion: go1.18.4 ``` ## Your Environment Server setup and configuration: cloud, 4 VMs, 4 SN, 4 http qw, 4 s3 gw Operating System and version (uname -a): linux vedi 5.10.0-16-amd64 https://github.com/nspcc-dev/neofs-node/issues/1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux

sami

2025-12-28 17:21:01 +00:00

closed this issue
added the
bug

U0
labels

sami commented

2025-12-28 17:21:01 +00:00

Author

Owner

@fyrchik commented on GitHub (Nov 15, 2022):

For the first 3 requests:

Nov 14 15:00:35 az neofs-s3-gw[14706]: 2022-11-14T15:00:35.018Z        error        handler/util.go:29        call method        {"status": 500, "request_id": "3b57c1a4-ddab-4a65-932a-68ff1619eed5", "method": "PutObject", "bucket": "4c9bb65d-4280-4bcd-8e3b-000de5a9bd94", "object": "1dda1097-8485-435a-b03a-49e36a776172", "description": "could not upload object", "error": "save obje
ct via connection pool: init writing on API client: client failure: context deadline exceeded", "body close errors": []}

Nov 14 15:00:35 az neofs-s3-gw[14706]: 2022-11-14T15:00:35.223Z        error        handler/util.go:29        call method        {"status": 500, "request_id": "a6f1822b-7407-4136-b487-3023c7f6766f", "method": "PutObject", "bucket": "8c9d8e85-138f-44b6-95dd-91ec048e9219", "object": "6bfcfd26-775b-4e19-a19f-5b56caa9db18", "description": "could not upload object", "error": "save object via connection pool: init writing on API client: client failure: context deadline exceeded", "body close errors": []}

Nov 14 15:00:35 az neofs-s3-gw[14706]: 2022-11-14T15:00:35.483Z        error        handler/util.go:29        call method        {"status": 500, "request_id": "38a269ac-87ee-412f-99b7-496c6cf128b3", "method": "PutObject", "bucket": "4c9bb65d-4280-4bcd-8e3b-000de5a9bd94", "object": "87ff709d-ad28-4408-a89b-abf6e61bc761", "description": "could not upload object", "error": "save object via connection pool: init writing on API client: client failure: context deadline exceeded", "body close errors": []}

context cancelled errors are expected under load in some configurations.

@fyrchik commented on GitHub (Nov 15, 2022): For the first 3 requests: ``` Nov 14 15:00:35 az neofs-s3-gw[14706]: 2022-11-14T15:00:35.018Z error handler/util.go:29 call method {"status": 500, "request_id": "3b57c1a4-ddab-4a65-932a-68ff1619eed5", "method": "PutObject", "bucket": "4c9bb65d-4280-4bcd-8e3b-000de5a9bd94", "object": "1dda1097-8485-435a-b03a-49e36a776172", "description": "could not upload object", "error": "save obje ct via connection pool: init writing on API client: client failure: context deadline exceeded", "body close errors": []} Nov 14 15:00:35 az neofs-s3-gw[14706]: 2022-11-14T15:00:35.223Z error handler/util.go:29 call method {"status": 500, "request_id": "a6f1822b-7407-4136-b487-3023c7f6766f", "method": "PutObject", "bucket": "8c9d8e85-138f-44b6-95dd-91ec048e9219", "object": "6bfcfd26-775b-4e19-a19f-5b56caa9db18", "description": "could not upload object", "error": "save object via connection pool: init writing on API client: client failure: context deadline exceeded", "body close errors": []} Nov 14 15:00:35 az neofs-s3-gw[14706]: 2022-11-14T15:00:35.483Z error handler/util.go:29 call method {"status": 500, "request_id": "38a269ac-87ee-412f-99b7-496c6cf128b3", "method": "PutObject", "bucket": "4c9bb65d-4280-4bcd-8e3b-000de5a9bd94", "object": "87ff709d-ad28-4408-a89b-abf6e61bc761", "description": "could not upload object", "error": "save object via connection pool: init writing on API client: client failure: context deadline exceeded", "body close errors": []} ``` `context cancelled` errors are expected under load in some configurations.

sami commented

2025-12-28 17:21:01 +00:00

Author

Owner

@fyrchik commented on GitHub (Nov 18, 2022):

S3 timeout issue

@fyrchik commented on GitHub (Nov 18, 2022): S3 timeout issue

sami commented

2025-12-28 17:21:01 +00:00

Author

Owner

@anikeev-yadro commented on GitHub (Nov 21, 2022):

This is the not timeout issue, beacuse change stream_timeout not addressed issue.
stream_timeout=10s and object size=64Kb, 18 operations was failed

aws_obj_put_fails......: 14 0.116272/s 
aws_obj_put_total......: 1023 8.496197/s

stream_timeout=20s, obect seize=64Kb, one operation was failed:

aws_obj_put_fails......: 1 0.008283/s 
aws_obj_put_total......: 862 7.139838/s

but when we increased obejct size to 10Mb (stream_timeout=20s) we had 29 fails again:

aws_obj_put_fails......: 29     0.187581/s
aws_obj_put_total......: 67     0.433377/s
```

@anikeev-yadro commented on GitHub (Nov 21, 2022): This is the not timeout issue, beacuse change ```stream_timeout``` not addressed issue. stream_timeout=10s and object size=64Kb, 18 operations was failed ``` aws_obj_put_fails......: 14 0.116272/s aws_obj_put_total......: 1023 8.496197/s ``` stream_timeout=20s, obect seize=64Kb, one operation was failed: ``` aws_obj_put_fails......: 1 0.008283/s aws_obj_put_total......: 862 7.139838/s ``` but when we increased obejct size to 10Mb (stream_timeout=20s) we had 29 fails again: ```` aws_obj_put_fails......: 29 0.187581/s aws_obj_put_total......: 67 0.433377/s ```

sami commented

2025-12-28 17:21:01 +00:00

Author

Owner

@fyrchik commented on GitHub (Nov 21, 2022):

@anikeev-yadro What was the stream_timeout in both neofs-storage and s3-gw?

@fyrchik commented on GitHub (Nov 21, 2022): @anikeev-yadro What was the `stream_timeout` in both `neofs-storage` and `s3-gw`?

sami commented

2025-12-28 17:21:01 +00:00

Author

Owner

@anikeev-yadro commented on GitHub (Nov 25, 2022):

neofs-storage:

apiclient:
  dial_timeout: 1s
  stream_timeout: 9s

s3-gw:

stream_timeout: 20s

@anikeev-yadro commented on GitHub (Nov 25, 2022): neofs-storage: ``` apiclient: dial_timeout: 1s stream_timeout: 9s ``` s3-gw: ``` stream_timeout: 20s ```

sami commented

2025-12-28 17:21:02 +00:00

Author

Owner

@anikeev-yadro commented on GitHub (Dec 30, 2022):

Not reproduced on 10 VUs in k6, but reproduced always on >40 VUs and 201 Mb object size.

@anikeev-yadro commented on GitHub (Dec 30, 2022): Not reproduced on 10 VUs in k6, but reproduced always on >40 VUs and 201 Mb object size.

sami commented

2025-12-28 17:21:02 +00:00

Author

Owner

@fyrchik commented on GitHub (Dec 31, 2022):