Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

receive: Cannot use optimized multi part upload. #3518

Closed
bwplotka opened this issue Nov 30, 2020 · 7 comments
Closed

receive: Cannot use optimized multi part upload. #3518

bwplotka opened this issue Nov 30, 2020 · 7 comments

Comments

@bwplotka
Copy link
Member

level=warn ts=2020-11-30T09:00:18.067006266Z caller=s3.go:399 component=receive msg="could not guess file size for multipart upload; upload might be not optimized" name=debug/metas/01ERC63277SJSMAQ2P1W132BH6.json err="unsupported type of io.Reader"

Sad outcome of dynamic casting ):

Help wanted 🤗

johncming added a commit to johncming/thanos that referenced this issue Nov 30, 2020
Fix issue thanos-io#3518

Signed-off-by: johncming <johncming@yahoo.com>
johncming added a commit to johncming/thanos that referenced this issue Nov 30, 2020
Fix issue thanos-io#3518

Signed-off-by: johncming <johncming@yahoo.com>
@GiedriusS
Copy link
Member

#3476

bwplotka pushed a commit that referenced this issue Nov 30, 2020
Fix issue #3518

Signed-off-by: johncming <johncming@yahoo.com>
@erdong
Copy link

erdong commented Dec 4, 2020

I had the same problem. Thanos version is 0.17.0 .

When will this fixed version be released ?

@keyhana
Copy link

keyhana commented Dec 4, 2020

Same here. After upgrading from 0.16.0 to 0.17.1 we are getting this warning from Thanos sidecar and Thanos compactor.
It is also causing high memory usage after the warning is printed which ultimately gets our pods OOMKilled.

@ethernoy
Copy link
Contributor

ethernoy commented Dec 5, 2020

same here, but the compactor seems to be working though, is it just a warning or it actually stops sth from working?

@ahurtaud
Copy link
Contributor

Hello, can we get an update on the PR #3476 and so on this issue please?

We cannot load v0.17.x because of this and we would like not to miss it on 0.18 :).

Thank you

@mfuezesi
Copy link

Hello there
Really like your work. But now I have the same problem. v16 works, v17 not. With the same issue. Is there another workaround?

@GiedriusS
Copy link
Member

Fixed in #3476.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants