[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[
https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=748036&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-748036
]
ASF GitHub Bot logged work on HADOOP-18028:
---
Author: ASF GitHub Bot
Created on: 25/Mar/22 21:48
Start Date: 25/Mar/22 21:48
Worklog Time Spent: 10m
Work Description: hadoop-yetus commented on pull request #4109:
URL: https://github.com/apache/hadoop/pull/4109#issuecomment-1079461106
:confetti_ball: **+1 overall**
| Vote | Subsystem | Runtime | Logfile | Comment |
|::|--:|:|::|:---:|
| +0 :ok: | reexec | 0m 37s | | Docker mode activated. |
_ Prechecks _ |
| +1 :green_heart: | dupname | 0m 1s | | No case conflicting files
found. |
| +0 :ok: | codespell | 0m 1s | | codespell was not available. |
| +0 :ok: | markdownlint | 0m 1s | | markdownlint was not available.
|
| +1 :green_heart: | @author | 0m 0s | | The patch does not contain
any @author tags. |
| +1 :green_heart: | test4tests | 0m 0s | | The patch appears to
include 21 new or modified test files. |
_ feature-HADOOP-18028-s3a-prefetch Compile Tests _ |
| +1 :green_heart: | mvninstall | 34m 21s | |
feature-HADOOP-18028-s3a-prefetch passed |
| +1 :green_heart: | compile | 0m 43s | |
feature-HADOOP-18028-s3a-prefetch passed with JDK
Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04 |
| +1 :green_heart: | compile | 0m 37s | |
feature-HADOOP-18028-s3a-prefetch passed with JDK Private
Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 |
| +1 :green_heart: | checkstyle | 0m 23s | |
feature-HADOOP-18028-s3a-prefetch passed |
| +1 :green_heart: | mvnsite | 0m 41s | |
feature-HADOOP-18028-s3a-prefetch passed |
| +1 :green_heart: | javadoc | 0m 24s | |
feature-HADOOP-18028-s3a-prefetch passed with JDK
Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04 |
| +1 :green_heart: | javadoc | 0m 30s | |
feature-HADOOP-18028-s3a-prefetch passed with JDK Private
Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 |
| +1 :green_heart: | spotbugs | 1m 7s | |
feature-HADOOP-18028-s3a-prefetch passed |
| +1 :green_heart: | shadedclient | 21m 24s | | branch has no errors
when building and testing our client artifacts. |
_ Patch Compile Tests _ |
| +1 :green_heart: | mvninstall | 0m 40s | | the patch passed |
| +1 :green_heart: | compile | 0m 39s | | the patch passed with JDK
Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04 |
| +1 :green_heart: | javac | 0m 39s | | the patch passed |
| +1 :green_heart: | compile | 0m 29s | | the patch passed with JDK
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 |
| +1 :green_heart: | javac | 0m 29s | | the patch passed |
| +1 :green_heart: | blanks | 0m 0s | | The patch has no blanks
issues. |
| +1 :green_heart: | checkstyle | 0m 19s | | hadoop-tools/hadoop-aws:
The patch generated 0 new + 5 unchanged - 2 fixed = 5 total (was 7) |
| +1 :green_heart: | mvnsite | 0m 39s | | the patch passed |
| +1 :green_heart: | xml | 0m 1s | | The patch has no ill-formed XML
file. |
| +1 :green_heart: | javadoc | 0m 19s | | the patch passed with JDK
Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04 |
| +1 :green_heart: | javadoc | 0m 26s | | the patch passed with JDK
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 |
| +1 :green_heart: | spotbugs | 1m 9s | | the patch passed |
| +1 :green_heart: | shadedclient | 20m 26s | | patch has no errors
when building and testing our client artifacts. |
_ Other Tests _ |
| +1 :green_heart: | unit | 2m 30s | | hadoop-aws in the patch passed.
|
| +1 :green_heart: | asflicense | 0m 32s | | The patch does not
generate ASF License warnings. |
| | | 89m 59s | | |
| Subsystem | Report/Notes |
|--:|:-|
| Docker | ClientAPI=1.41 ServerAPI=1.41 base:
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4109/1/artifact/out/Dockerfile
|
| GITHUB PR | https://github.com/apache/hadoop/pull/4109 |
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient codespell xml spotbugs checkstyle markdownlint |
| uname | Linux 188f1fde1f74 4.15.0-161-generic #169-Ubuntu SMP Fri Oct 15
13:41:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/bin/hadoop.sh |
| git revision | feature-HADOOP-18028-s3a-prefetch /
c8885271e70deb233fdbd4dfd6d45711e667c8da |
| Default Java | Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 |
| Multi-JDK versions |
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04
/usr/lib/jvm/java-8-open
[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[ https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=748350&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-748350 ] ASF GitHub Bot logged work on HADOOP-18028: --- Author: ASF GitHub Bot Created on: 27/Mar/22 17:36 Start Date: 27/Mar/22 17:36 Worklog Time Spent: 10m Work Description: pjfanning commented on pull request #4109: URL: https://github.com/apache/hadoop/pull/4109#issuecomment-1079981138 @steveloughran twitter futures should be fairly easily replace with [Java futures](https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/Future.html) * this seems to a fairly good description of the twitter FuturePool - https://blog.knoldus.com/twitter-future-in-scala/ * should be possible to port it to Java easily enough -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 748350) Time Spent: 12h 50m (was: 12h 40m) > High performance S3A input stream with prefetching & caching > > > Key: HADOOP-18028 > URL: https://issues.apache.org/jira/browse/HADOOP-18028 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Reporter: Bhalchandra Pandit >Assignee: Bhalchandra Pandit >Priority: Major > Labels: pull-request-available > Time Spent: 12h 50m > Remaining Estimate: 0h > > I work for Pinterest. I developed a technique for vastly improving read > throughput when reading from the S3 file system. It not only helps the > sequential read case (like reading a SequenceFile) but also significantly > improves read throughput of a random access case (like reading Parquet). This > technique has been very useful in significantly improving efficiency of the > data processing jobs at Pinterest. > > I would like to contribute that feature to Apache Hadoop. More details on > this technique are available in this blog I wrote recently: > [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0] > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[ https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=748351&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-748351 ] ASF GitHub Bot logged work on HADOOP-18028: --- Author: ASF GitHub Bot Created on: 27/Mar/22 17:36 Start Date: 27/Mar/22 17:36 Worklog Time Spent: 10m Work Description: pjfanning edited a comment on pull request #4109: URL: https://github.com/apache/hadoop/pull/4109#issuecomment-1079981138 @steveloughran twitter futures should be fairly easily replaced with [Java futures](https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/Future.html) * this seems to a fairly good description of the twitter FuturePool - https://blog.knoldus.com/twitter-future-in-scala/ * should be possible to port it to Java easily enough -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 748351) Time Spent: 13h (was: 12h 50m) > High performance S3A input stream with prefetching & caching > > > Key: HADOOP-18028 > URL: https://issues.apache.org/jira/browse/HADOOP-18028 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Reporter: Bhalchandra Pandit >Assignee: Bhalchandra Pandit >Priority: Major > Labels: pull-request-available > Time Spent: 13h > Remaining Estimate: 0h > > I work for Pinterest. I developed a technique for vastly improving read > throughput when reading from the S3 file system. It not only helps the > sequential read case (like reading a SequenceFile) but also significantly > improves read throughput of a random access case (like reading Parquet). This > technique has been very useful in significantly improving efficiency of the > data processing jobs at Pinterest. > > I would like to contribute that feature to Apache Hadoop. More details on > this technique are available in this blog I wrote recently: > [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0] > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[ https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=748352&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-748352 ] ASF GitHub Bot logged work on HADOOP-18028: --- Author: ASF GitHub Bot Created on: 27/Mar/22 17:42 Start Date: 27/Mar/22 17:42 Worklog Time Spent: 10m Work Description: pjfanning edited a comment on pull request #4109: URL: https://github.com/apache/hadoop/pull/4109#issuecomment-1079981138 @steveloughran twitter futures should be fairly easily replaced with [Java futures](https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/Future.html) * this seems to a fairly good description of the twitter FuturePool - https://blog.knoldus.com/twitter-future-in-scala/ * should be possible to port it to Java easily enough * it may even not be necessary to port the twitter FuturePool because it appears its main use to help Scala users avoid having to deal Java futures used in AWS code (cf https://medium.com/@sveinnfannar/thread-pooling-in-scala-using-twitter-s-futurepool-8f38c6448fa2) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 748352) Time Spent: 13h 10m (was: 13h) > High performance S3A input stream with prefetching & caching > > > Key: HADOOP-18028 > URL: https://issues.apache.org/jira/browse/HADOOP-18028 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Reporter: Bhalchandra Pandit >Assignee: Bhalchandra Pandit >Priority: Major > Labels: pull-request-available > Time Spent: 13h 10m > Remaining Estimate: 0h > > I work for Pinterest. I developed a technique for vastly improving read > throughput when reading from the S3 file system. It not only helps the > sequential read case (like reading a SequenceFile) but also significantly > improves read throughput of a random access case (like reading Parquet). This > technique has been very useful in significantly improving efficiency of the > data processing jobs at Pinterest. > > I would like to contribute that feature to Apache Hadoop. More details on > this technique are available in this blog I wrote recently: > [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0] > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[ https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=748516&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-748516 ] ASF GitHub Bot logged work on HADOOP-18028: --- Author: ASF GitHub Bot Created on: 28/Mar/22 10:05 Start Date: 28/Mar/22 10:05 Worklog Time Spent: 10m Work Description: steveloughran merged pull request #4109: URL: https://github.com/apache/hadoop/pull/4109 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 748516) Time Spent: 13h 20m (was: 13h 10m) > High performance S3A input stream with prefetching & caching > > > Key: HADOOP-18028 > URL: https://issues.apache.org/jira/browse/HADOOP-18028 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Reporter: Bhalchandra Pandit >Assignee: Bhalchandra Pandit >Priority: Major > Labels: pull-request-available > Time Spent: 13h 20m > Remaining Estimate: 0h > > I work for Pinterest. I developed a technique for vastly improving read > throughput when reading from the S3 file system. It not only helps the > sequential read case (like reading a SequenceFile) but also significantly > improves read throughput of a random access case (like reading Parquet). This > technique has been very useful in significantly improving efficiency of the > data processing jobs at Pinterest. > > I would like to contribute that feature to Apache Hadoop. More details on > this technique are available in this blog I wrote recently: > [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0] > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[ https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=748535&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-748535 ] ASF GitHub Bot logged work on HADOOP-18028: --- Author: ASF GitHub Bot Created on: 28/Mar/22 10:57 Start Date: 28/Mar/22 10:57 Worklog Time Spent: 10m Work Description: pjfanning edited a comment on pull request #4109: URL: https://github.com/apache/hadoop/pull/4109#issuecomment-1079981138 @steveloughran twitter futures should be fairly easily replaced with [Java futures](https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/Future.html) * this seems to a fairly good description of the twitter FuturePool - https://blog.knoldus.com/twitter-future-in-scala/ * should be possible to port it to Java easily enough * it may even not be necessary to port the twitter FuturePool because it appears its main use to help Scala users avoid having to deal Java futures used in AWS code (cf https://medium.com/@sveinnfannar/thread-pooling-in-scala-using-twitter-s-futurepool-8f38c6448fa2) I have an example change - https://github.com/steveloughran/hadoop/pull/2 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 748535) Time Spent: 13.5h (was: 13h 20m) > High performance S3A input stream with prefetching & caching > > > Key: HADOOP-18028 > URL: https://issues.apache.org/jira/browse/HADOOP-18028 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Reporter: Bhalchandra Pandit >Assignee: Bhalchandra Pandit >Priority: Major > Labels: pull-request-available > Time Spent: 13.5h > Remaining Estimate: 0h > > I work for Pinterest. I developed a technique for vastly improving read > throughput when reading from the S3 file system. It not only helps the > sequential read case (like reading a SequenceFile) but also significantly > improves read throughput of a random access case (like reading Parquet). This > technique has been very useful in significantly improving efficiency of the > data processing jobs at Pinterest. > > I would like to contribute that feature to Apache Hadoop. More details on > this technique are available in this blog I wrote recently: > [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0] > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[ https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=749290&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-749290 ] ASF GitHub Bot logged work on HADOOP-18028: --- Author: ASF GitHub Bot Created on: 29/Mar/22 12:21 Start Date: 29/Mar/22 12:21 Worklog Time Spent: 10m Work Description: steveloughran closed pull request #3736: URL: https://github.com/apache/hadoop/pull/3736 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 749290) Time Spent: 13h 40m (was: 13.5h) > High performance S3A input stream with prefetching & caching > > > Key: HADOOP-18028 > URL: https://issues.apache.org/jira/browse/HADOOP-18028 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Reporter: Bhalchandra Pandit >Assignee: Bhalchandra Pandit >Priority: Major > Labels: pull-request-available > Time Spent: 13h 40m > Remaining Estimate: 0h > > I work for Pinterest. I developed a technique for vastly improving read > throughput when reading from the S3 file system. It not only helps the > sequential read case (like reading a SequenceFile) but also significantly > improves read throughput of a random access case (like reading Parquet). This > technique has been very useful in significantly improving efficiency of the > data processing jobs at Pinterest. > > I would like to contribute that feature to Apache Hadoop. More details on > this technique are available in this blog I wrote recently: > [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0] > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[ https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=749291&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-749291 ] ASF GitHub Bot logged work on HADOOP-18028: --- Author: ASF GitHub Bot Created on: 29/Mar/22 12:21 Start Date: 29/Mar/22 12:21 Worklog Time Spent: 10m Work Description: steveloughran commented on pull request #3736: URL: https://github.com/apache/hadoop/pull/3736#issuecomment-1081802033 patch is merged in to the feature branch; closing this to avoid confusion. thank you for a wonderful contribution! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 749291) Time Spent: 13h 50m (was: 13h 40m) > High performance S3A input stream with prefetching & caching > > > Key: HADOOP-18028 > URL: https://issues.apache.org/jira/browse/HADOOP-18028 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Reporter: Bhalchandra Pandit >Assignee: Bhalchandra Pandit >Priority: Major > Labels: pull-request-available > Time Spent: 13h 50m > Remaining Estimate: 0h > > I work for Pinterest. I developed a technique for vastly improving read > throughput when reading from the S3 file system. It not only helps the > sequential read case (like reading a SequenceFile) but also significantly > improves read throughput of a random access case (like reading Parquet). This > technique has been very useful in significantly improving efficiency of the > data processing jobs at Pinterest. > > I would like to contribute that feature to Apache Hadoop. More details on > this technique are available in this blog I wrote recently: > [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0] > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[ https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=796067&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796067 ] ASF GitHub Bot logged work on HADOOP-18028: --- Author: ASF GitHub Bot Created on: 28/Jul/22 13:28 Start Date: 28/Jul/22 13:28 Worklog Time Spent: 10m Work Description: steveloughran opened a new pull request, #4654: URL: https://github.com/apache/hadoop/pull/4654 ### Description of PR This is the feature branch feature/HADOOP-18028-s3a-prefetch rebased on trunk to see how yetus likes it. If all is good I will force push it to the asf branch, so things are up to date. rebase merge issues * Constants, docs * S3AReadOpsContext some compilation errors to fix ### How was this patch tested? ### For code changes: - [ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')? - [ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, `NOTICE-binary` files? Issue Time Tracking --- Worklog Id: (was: 796067) Time Spent: 14h (was: 13h 50m) > High performance S3A input stream with prefetching & caching > > > Key: HADOOP-18028 > URL: https://issues.apache.org/jira/browse/HADOOP-18028 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Reporter: Bhalchandra Pandit >Assignee: Bhalchandra Pandit >Priority: Major > Labels: pull-request-available > Time Spent: 14h > Remaining Estimate: 0h > > I work for Pinterest. I developed a technique for vastly improving read > throughput when reading from the S3 file system. It not only helps the > sequential read case (like reading a SequenceFile) but also significantly > improves read throughput of a random access case (like reading Parquet). This > technique has been very useful in significantly improving efficiency of the > data processing jobs at Pinterest. > > I would like to contribute that feature to Apache Hadoop. More details on > this technique are available in this blog I wrote recently: > [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Work logged] (HADOOP-18028) High performance S3A input stream with prefetching & caching
[ https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=797311&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-797311 ] ASF GitHub Bot logged work on HADOOP-18028: --- Author: ASF GitHub Bot Created on: 02/Aug/22 17:12 Start Date: 02/Aug/22 17:12 Worklog Time Spent: 10m Work Description: steveloughran opened a new pull request, #4675: URL: https://github.com/apache/hadoop/pull/4675 This is the commit chain of feature-HADOOP-18028-s3a-prefetch rebased to trunk and with a fixup at the end. I intend to apply this chain to the feature branch with a goal of a squash and merge of the branch into trunk ASAP, with all final work done on trunk ### How was this patch tested? s3 london, params `-Dparallel-tests -DtestsThreadCount=8 -Dscale` all new failures reported * [HADOOP-18386](https://issues.apache.org/jira/browse/HADOOP-18386) ITestS3SelectLandsat timeout after 10 minutes. surfaces in trunk too. * [HADOOP-18384](https://issues.apache.org/jira/browse/HADOOP-18384) ITestS3AFileSystemStatistic failure in prefetch feature branch * [HADOOP-18385](https://issues.apache.org/jira/browse/HADOOP-18385) ITestS3ACannedACLs failure; not in a span. I don't believe any are related, rather that changing the #of tests triggered latent issues surfacing from different states of the jvm before each suite, or, in the case of the landsat one, some change in the endpoint. ### For code changes: - [X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')? - [X] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, `NOTICE-binary` files? Issue Time Tracking --- Worklog Id: (was: 797311) Time Spent: 14h 10m (was: 14h) > High performance S3A input stream with prefetching & caching > > > Key: HADOOP-18028 > URL: https://issues.apache.org/jira/browse/HADOOP-18028 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Reporter: Bhalchandra Pandit >Assignee: Bhalchandra Pandit >Priority: Major > Labels: pull-request-available > Time Spent: 14h 10m > Remaining Estimate: 0h > > I work for Pinterest. I developed a technique for vastly improving read > throughput when reading from the S3 file system. It not only helps the > sequential read case (like reading a SequenceFile) but also significantly > improves read throughput of a random access case (like reading Parquet). This > technique has been very useful in significantly improving efficiency of the > data processing jobs at Pinterest. > > I would like to contribute that feature to Apache Hadoop. More details on > this technique are available in this blog I wrote recently: > [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
