[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: HADOOP-14475.005.patch update: 1.remove streamMetrics hashmap, register all metrics into

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: HADOOP-14475.006.patch update: 1.add ASF license for new test class > Metrics of S3A don't

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128548#comment-16128548 ] Yonger commented on HADOOP-14475: - [~ste...@apache.org] Can you help to verify and review this patch?

[jira] [Commented] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128838#comment-16128838 ] Yonger commented on HADOOP-14774: - I saw the doc of withRange said : * The first byte in an object

[jira] [Issue Comment Deleted] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14774: Comment: was deleted (was: I saw the doc of withRange said : * The first byte in an object has

[jira] [Updated] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14774: Description: {code:java} Running org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance Tests

[jira] [Commented] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126990#comment-16126990 ] Yonger commented on HADOOP-14774: - {code:java} GetObjectRequest request = new

[jira] [Created] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

Yonger created HADOOP-14774: --- Summary: S3A case "testRandomReadOverBuffer" failed due to improper range parameter Key: HADOOP-14774 URL: https://issues.apache.org/jira/browse/HADOOP-14774 Project: Hadoop

[jira] [Assigned] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger reassigned HADOOP-14774: --- Assignee: Yonger > S3A case "testRandomReadOverBuffer" failed due to improper range parameter >

[jira] [Commented] (HADOOP-14770) S3A http connection in s3a driver not reuse in Spark application

[ https://issues.apache.org/jira/browse/HADOOP-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127218#comment-16127218 ] Yonger commented on HADOOP-14770: - Sorry, not yet. I am working with multiple partners on our big data

[jira] [Updated] (HADOOP-14770) S3A http connection in s3a driver not reuse in Spark application

[ https://issues.apache.org/jira/browse/HADOOP-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14770: Affects Version/s: 2.7.3 > S3A http connection in s3a driver not reuse in Spark application >

[jira] [Updated] (HADOOP-14770) S3A http connection in s3a driver not reuse in Spark application

[ https://issues.apache.org/jira/browse/HADOOP-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14770: Component/s: fs/s3 > S3A http connection in s3a driver not reuse in Spark application >

[jira] [Created] (HADOOP-14770) S3A http connection in s3a driver not reuse in Spark application

Yonger created HADOOP-14770: --- Summary: S3A http connection in s3a driver not reuse in Spark application Key: HADOOP-14770 URL: https://issues.apache.org/jira/browse/HADOOP-14770 Project: Hadoop Common

[jira] [Commented] (HADOOP-14770) S3A http connection in s3a driver not reuse in Spark application

[ https://issues.apache.org/jira/browse/HADOOP-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125536#comment-16125536 ] Yonger commented on HADOOP-14770: - Thanks Steve, the application running on Hadoop 2.7.3 and against ORC

[jira] [Assigned] (HADOOP-14770) S3A http connection in s3a driver not reuse in Spark application

[ https://issues.apache.org/jira/browse/HADOOP-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger reassigned HADOOP-14770: --- Assignee: Yonger > S3A http connection in s3a driver not reuse in Spark application >

[jira] [Commented] (HADOOP-13637) improve setting of max connections in AWS client

[ https://issues.apache.org/jira/browse/HADOOP-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094592#comment-16094592 ] Yonger commented on HADOOP-13637: - [~steve_l] I don't think we should create a connection pool bigger

[jira] [Commented] (HADOOP-13757) Remove verifyBuckets overhead in S3AFileSystem::initialize()

[ https://issues.apache.org/jira/browse/HADOOP-13757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094598#comment-16094598 ] Yonger commented on HADOOP-13757: - [~ste...@apache.org]Can you give more specific suggestion on this

[jira] [Comment Edited] (HADOOP-13637) improve setting of max connections in AWS client

[ https://issues.apache.org/jira/browse/HADOOP-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094592#comment-16094592 ] Yonger edited comment on HADOOP-13637 at 7/20/17 12:13 PM: ---

[jira] [Commented] (HADOOP-13845) s3a to instrument duration of HTTP calls

[ https://issues.apache.org/jira/browse/HADOOP-13845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095706#comment-16095706 ] Yonger commented on HADOOP-13845: - Another usage is push http duration into database(such as influxdb),

[jira] [Commented] (HADOOP-13762) S3A: Set thread names with more specific information about the call.

[ https://issues.apache.org/jira/browse/HADOOP-13762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095684#comment-16095684 ] Yonger commented on HADOOP-13762: - I agree a thread name with meaningful information is a great idea,

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100142#comment-16100142 ] Yonger commented on HADOOP-14475: - [~ste...@apache.org] I found the output of metrics missing part of

[jira] [Commented] (HADOOP-13845) s3a to instrument duration of HTTP calls

[ https://issues.apache.org/jira/browse/HADOOP-13845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098416#comment-16098416 ] Yonger commented on HADOOP-13845: - Does this make sense? {code:java} Duration duration = new

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: failsafe-report-scale.html failsafe-report-scale.zip Only one case failed.

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: HADOOP-14475-003.patch compliant with raw code format and update the logic of metrics

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076511#comment-16076511 ] Yonger commented on HADOOP-14475: - [~stevea] the method you mentioned give an empty url to skip the

[jira] [Comment Edited] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076511#comment-16076511 ] Yonger edited comment on HADOOP-14475 at 7/6/17 1:42 PM: - @steve the method you

[jira] [Created] (HADOOP-14745) s3a getFileStatus can't return expect result when existing a file and directory with the same name

Yonger created HADOOP-14745: --- Summary: s3a getFileStatus can't return expect result when existing a file and directory with the same name Key: HADOOP-14745 URL: https://issues.apache.org/jira/browse/HADOOP-14745

[jira] [Commented] (HADOOP-14745) s3a getFileStatus can't return expect result when existing a file and directory with the same name

[ https://issues.apache.org/jira/browse/HADOOP-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118009#comment-16118009 ] Yonger commented on HADOOP-14745: - So i think we should call getFileStatus with explicitly expect, e.g.

[jira] [Commented] (HADOOP-14745) s3a getFileStatus can't return expect result when existing a file and directory with the same name

[ https://issues.apache.org/jira/browse/HADOOP-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118026#comment-16118026 ] Yonger commented on HADOOP-14745: - On the other hand, I saw hdfs implementation not allow existing any

[jira] [Commented] (HADOOP-14745) s3a getFileStatus can't return expect result when existing a file and directory with the same name

[ https://issues.apache.org/jira/browse/HADOOP-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118177#comment-16118177 ] Yonger commented on HADOOP-14745: - I create that path structure through s3cmd, and yes , we can't do

[jira] [Commented] (HADOOP-13430) Optimize and fix getFileStatus in S3A

[ https://issues.apache.org/jira/browse/HADOOP-13430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116700#comment-16116700 ] Yonger commented on HADOOP-13430: - [~ste...@apache.org] I really can't see any optimization for

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056807#comment-16056807 ] Yonger commented on HADOOP-14475: - @Deng, each task should have an individual s3a file system that i

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Release Note: (was: fix S3AInstrumentation registration issue ) Status: Patch Available (was:

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: failsafe-report-s3a-it.html > Metrics of S3A don't print out when enable it in Hadoop

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Status: Open (was: Patch Available) > Metrics of S3A don't print out when enable it in Hadoop metrics

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: HADOOP-14475.002.patch > Metrics of S3A don't print out when enable it in Hadoop metrics

[jira] [Comment Edited] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058815#comment-16058815 ] Yonger edited comment on HADOOP-14475 at 6/22/17 6:18 AM: -- Fixed this issue by

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: (was: failsafe-report-it.html) > Metrics of S3A don't print out when enable it in Hadoop

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: failsafe-report-it.html failsafe-report-s3a-scale.html I run cases on Ceph

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Component/s: (was: s3) fs/s3 > Metrics of S3A don't print out when enable it in

[jira] [Comment Edited] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037032#comment-16037032 ] Yonger edited comment on HADOOP-14475 at 6/5/17 2:28 PM: - This patch can fix the

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: s3a-metrics.patch1 This patch can fix the issue that s3a metrics don't print out to

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Release Note: fix S3AInstrumentation registration issue Status: Patch Available (was: Open) >

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16040018#comment-16040018 ] Yonger commented on HADOOP-14475: - In my case, i just run DFSIO with 20 map/reduce tasks in a 4-nodes

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: stdout.zip > Metrics of S3A don't print out when enable it in Hadoop metrics property file >

[jira] [Created] (HADOOP-14475) Metrics of S3A doesn't print out when enable it in Hadoop metrics property file

Yonger created HADOOP-14475: --- Summary: Metrics of S3A doesn't print out when enable it in Hadoop metrics property file Key: HADOOP-14475 URL: https://issues.apache.org/jira/browse/HADOOP-14475 Project:

[jira] [Updated] (HADOOP-14475) Metrics of S3A doesn't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Description: *.sink.file.class=org.apache.hadoop.metrics2.sink.FileSink

[jira] [Updated] (HADOOP-14475) Metrics of S3A doesn't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Description: *.sink.file.class=org.apache.hadoop.metrics2.sink.FileSink

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Summary: Metrics of S3A don't print out when enable it in Hadoop metrics property file (was: Metrics of

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038864#comment-16038864 ] Yonger commented on HADOOP-14475: - Thanks for your suggestion. I will take case for code style and do

[jira] [Resolved] (HADOOP-14770) S3A http connection in s3a driver not reuse in Spark application

[ https://issues.apache.org/jira/browse/HADOOP-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger resolved HADOOP-14770. - Resolution: Duplicate Thanks Steve. when we apply the read input policy with random in our workload

[jira] [Updated] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14774: Attachment: HADOOP-14774.003.patch > S3A case "testRandomReadOverBuffer" failed due to improper range

[jira] [Commented] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16156959#comment-16156959 ] Yonger commented on HADOOP-14774: - [~ste...@apache.org] Is the latest patch OK? > S3A case

[jira] [Updated] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14774: Attachment: HADOOP-14774.001.patch upload patch first since my s3-compatible storage backend not works

[jira] [Updated] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14774: Attachment: failsafe-report.html test against on Ceph object store over s3a. > S3A case

[jira] [Updated] (HADOOP-14774) S3A case "testRandomReadOverBuffer" failed due to improper range parameter

[ https://issues.apache.org/jira/browse/HADOOP-14774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14774: Attachment: HADOOP-14774.002.patch > S3A case "testRandomReadOverBuffer" failed due to improper range

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252804#comment-16252804 ] Yonger commented on HADOOP-14475: - For the # 2 point of my update --

[jira] [Comment Edited] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252804#comment-16252804 ] Yonger edited comment on HADOOP-14475 at 11/15/17 1:31 AM: --- For the # 2 point

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252798#comment-16252798 ] Yonger commented on HADOOP-14475: - [~macdonsp]the .008 patch is newer than .007 patch, I think it's the

[jira] [Comment Edited] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252804#comment-16252804 ] Yonger edited comment on HADOOP-14475 at 11/15/17 1:42 AM: --- For the # 2 point

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252976#comment-16252976 ] Yonger commented on HADOOP-14475: - [~mackrorysd]Thank you. > Metrics of S3A don't print out when

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266866#comment-16266866 ] Yonger commented on HADOOP-14475: - azure just give the registry name to the record, which is confused.

[jira] [Commented] (HADOOP-14943) Add common getFileBlockLocations() emulation for object stores, including S3A

[ https://issues.apache.org/jira/browse/HADOOP-14943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266856#comment-16266856 ] Yonger commented on HADOOP-14943: - [~ste...@apache.org]I remember there are some discussion about how to

[jira] [Comment Edited] (HADOOP-14943) Add common getFileBlockLocations() emulation for object stores, including S3A

[ https://issues.apache.org/jira/browse/HADOOP-14943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266856#comment-16266856 ] Yonger edited comment on HADOOP-14943 at 11/27/17 2:15 PM: ---

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268051#comment-16268051 ] Yonger commented on HADOOP-14475: - [~mackrorysd] So our final output format of record doesn't include

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268148#comment-16268148 ] Yonger commented on HADOOP-14475: - [~mackrorysd] Thank you. I start to understand your logic, and I

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: HADOOP-14475.008.patch update: 1.chang prefix and context name to dfs style 2.give each

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251020#comment-16251020 ] Yonger commented on HADOOP-14475: - [~mackrorysd] Thank you very much. For the test case, I removed the

[jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260436#comment-16260436 ] Yonger commented on HADOOP-14475: - [~mackrorysd]Thanks for refining the code, that looks pretty good for

[jira] [Comment Edited] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252804#comment-16252804 ] Yonger edited comment on HADOOP-14475 at 11/15/17 1:44 AM: --- For the # 2 point

[jira] [Commented] (HADOOP-15000) s3a new getdefaultblocksize be called in getFileStatus which has not been implemented in s3afilesystem yet

[ https://issues.apache.org/jira/browse/HADOOP-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16235037#comment-16235037 ] Yonger commented on HADOOP-15000: - Thanks for your detail interpretation. But s3a has it's own

[jira] [Created] (HADOOP-15000) s3a new getdefaultblocksize be called in getFileStatus which has not been implemented in s3afilesystem yet

Yonger created HADOOP-15000: --- Summary: s3a new getdefaultblocksize be called in getFileStatus which has not been implemented in s3afilesystem yet Key: HADOOP-15000 URL:

[jira] [Created] (HADOOP-15087) Write directly without creating temp directory to avoid rename

Yonger created HADOOP-15087: --- Summary: Write directly without creating temp directory to avoid rename Key: HADOOP-15087 URL: https://issues.apache.org/jira/browse/HADOOP-15087 Project: Hadoop Common

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Attachment: HADOOP-14775.007.patch based trunk. > Metrics of S3A don't print out when enable it in

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Status: Patch Available (was: Open) > Metrics of S3A don't print out when enable it in Hadoop metrics

[jira] [Updated] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file

[ https://issues.apache.org/jira/browse/HADOOP-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger updated HADOOP-14475: Status: Open (was: Patch Available) > Metrics of S3A don't print out when enable it in Hadoop metrics

[jira] [Resolved] (HADOOP-15182) Support to change back to signature version 2 of AWS SDK

[ https://issues.apache.org/jira/browse/HADOOP-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonger resolved HADOOP-15182. - Resolution: Not A Problem > Support to change back to signature version 2 of AWS SDK >

[jira] [Commented] (HADOOP-15182) Support to change back to signature version 2 of AWS SDK

[ https://issues.apache.org/jira/browse/HADOOP-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16333778#comment-16333778 ] Yonger commented on HADOOP-15182: - Just know how to roll back to signature v2, it's a bit hard to find

[jira] [Commented] (HADOOP-14943) Add common getFileBlockLocations() emulation for object stores, including S3A

[ https://issues.apache.org/jira/browse/HADOOP-14943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303790#comment-16303790 ] Yonger commented on HADOOP-14943: - [~ste...@apache.org] As Hadoop running on s3-compatible storage,

[jira] [Commented] (HADOOP-15182) Support to change back to signature version 2 of AWS SDK

[ https://issues.apache.org/jira/browse/HADOOP-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331554#comment-16331554 ] Yonger commented on HADOOP-15182: - You means  "fs.s3a.signing-algorithm"?, but I can't find an algorithm