HDDS-4993. Add guardrail for reserved buffer size when DN reads a chunk #2058
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Currently DN reserves a byte buffer for client's chunk read request based on whatever client specifies, without check. Client can send a message forcing DN to allocate up to 2GB memory per request.
This change makes DN reject read requests if chunk length specified by client is over the maximum allowed chunk size (32MB). Normally this should not happen, as chunk info is fetched before read from the server.
https://issues.apache.org/jira/browse/HDDS-4993
How was this patch tested?
Added unit test.
https://github.com/adoroszlai/hadoop-ozone/actions/runs/664486050