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

s3.upload() does not really support arbitrarily sized buffers #617

Closed
bkw opened this issue May 24, 2015 · 4 comments
Closed

s3.upload() does not really support arbitrarily sized buffers #617

bkw opened this issue May 24, 2015 · 4 comments
Labels
documentation This is a problem with documentation.

Comments

@bkw
Copy link
Contributor

bkw commented May 24, 2015

Streaming a big file to s3.upload() can cause the PartNumber parameter to overflow the allowed maximum of 10000, resulting in an InvalidArgument: Part number must be an integer between 1 and 10000 Error.

I managed to work around the problem by using a 10mb partSize, but I think the documentation should be updated to reflect this limitation.

btw, using a partSize of 20mb resulted in another failure:

(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
[…]

RangeError: Maximum call stack size exceeded
@lsegal
Copy link
Contributor

lsegal commented May 24, 2015

I managed to work around the problem by using a 10mb partSize, but I think the documentation should be updated to reflect this limitation.

If this is not mentioned in our docs I agree that it should be.

btw, using a partSize of 20mb resulted in another failure:

What version of Node.js are you using?

@bkw
Copy link
Contributor Author

bkw commented May 24, 2015

What version of Node.js are you using?

$ node --version
v0.10.38

@lsegal
Copy link
Contributor

lsegal commented May 24, 2015

I would suggest upgrading to 0.12. The Recursive nextTick issue is a known one in Node.js, see nodejs/node-v0.x-archive#6065.

@AdityaManohar AdityaManohar added the documentation This is a problem with documentation. label Jun 5, 2015
AdityaManohar added a commit that referenced this issue Aug 4, 2015
@lock
Copy link

lock bot commented Sep 29, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation This is a problem with documentation.
Projects
None yet
Development

No branches or pull requests

3 participants