-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Add position read supports for s3 proxy #18578
Add position read supports for s3 proxy #18578
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM, Hope to add some descriptions so that others can better understand
alluxio bot, merge this please |
merge failed: |
alluxio bot, merge this please |
alluxio-bot, cherry-pick this to branch-2.10 please |
### What changes are proposed in this pull request? When requesting a smaller range from the S3 proxy, support the S3 proxy in using the position read API to request data from the worker. add a new property: ``` alluxio.proxy.s3.use.position.read.range.size ``` ### Why are the changes needed? Using position read can effectively solve the issue of reading amplification. Please clarify why the changes are needed. For instance, 1. If you propose a new API, clarify the use case for a new API. no 2. If you fix a bug, describe the bug. no ### Does this PR introduce any user facing changes? Please list the user-facing changes introduced by your change, including 1. change in user-facing APIs no 2. addition or removal of property keys yes 3. webui no pr-link: #18578 change-id: cid-16bc766da5b13a1ca9acee4bea1151723a9f909d
Auto cherry-pick to branch |
Cherry-pick of existing commit. orig-pr: #18578 orig-commit: e56de13 orig-commit-author: humengyu <[email protected]> pr-link: #18579 change-id: cid-16bc766da5b13a1ca9acee4bea1151723a9f909d
What changes are proposed in this pull request?
When requesting a smaller range from the S3 proxy, support the S3 proxy in using the position read API to request data from the worker.
add a new property:
Why are the changes needed?
Using position read can effectively solve the issue of reading amplification.
Please clarify why the changes are needed. For instance,
Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including