Skip to content

Conversation

@roshan
Copy link
Contributor

@roshan roshan commented May 9, 2017

This is for the non-blocking server. This makes it so that just starting up something with all defaults won't result in it being possible to construct an input that causes it to OOME by just filling up the read buffer.

This is for the non-blocking server.
@roshan roshan changed the title Set default max read buffer size in Java server THRIFT-4193 Set default max read buffer size in Java server May 9, 2017
Copy link
Contributor

@jeking3 jeking3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

even 256MB seems like a huge I/O buffer to allow... shouldn't this be configurable by the consuming application?

@roshan
Copy link
Contributor Author

roshan commented May 10, 2017

It is configurable using the maxReadBufferBytes argument, but the default is just really high.

EDIT: Actually, that doesn't have a setter, but you can manipulate it directly.

@asfgit asfgit closed this in 3966a56 May 10, 2017
@roshan roshan deleted the THRIFT-4193 branch May 10, 2017 23:37
jeking3 pushed a commit to jeking3/thrift that referenced this pull request Aug 5, 2017
…vers

Client: Java
Patch: Roshan George <rgeorge@liveramp.com>

This closes apache#1264
jeking3 pushed a commit to jeking3/thrift that referenced this pull request Nov 30, 2017
…vers

Client: Java
Patch: Roshan George <rgeorge@liveramp.com>

This closes apache#1264
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants