Issue with chunk-signature when load testing with minio warp
dcarrion87 opened this issue · 1 comments
dcarrion87 commented
Version of sigv4 proxy is 1.6.
We're currently load testing throughput capabilities of the proxy and ran into this issue whilst testing with minio warp.
warp: <ERROR> unexpected download size. want:10485760, got:10500246
warp: <ERROR> unexpected download size. want:10485760, got:10500246
warp: <ERROR> unexpected download size. want:10485760, got:10500246
Looks like chunk-signature is ending up in the file:
10000;chunk-signature=7cc8934a07a23a0b069244e0f418202c055291dffeb9cf8bfa3b92df546b4aeb
If we go direct to the S3 endpoint we don't get this issue so aws-sigv4-proxy seems to be uploading with that chunk-signature in the file when using the tool?
Seems like this has been an issue before with other "servers". See: minio/warp#164
Ive also raised an issue here: minio/warp#232
dcarrion87 commented
We have decided not to use this service as the overheads were too great.