[ 
https://issues.apache.org/jira/browse/HADOOP-16612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969679#comment-16969679
 ] 

Hadoop QA commented on HADOOP-16612:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  9s{color} 
| {color:red} HADOOP-16612 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-16612 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12985290/HADOOP-16612-001.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/16644/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> Track Azure Blob File System client-perceived latency
> -----------------------------------------------------
>
>                 Key: HADOOP-16612
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16612
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure, hdfs-client
>            Reporter: Jeetesh Mangwani
>            Assignee: Jeetesh Mangwani
>            Priority: Major
>         Attachments: HADOOP-16612-001.patch
>
>
> Track the end-to-end performance of ADLS Gen 2 REST APIs by measuring latency 
> in the Hadoop ABFS driver.
> The latency information is sent back to the ADLS Gen 2 REST API endpoints in 
> the subsequent requests.
> Here's the PR: https://github.com/apache/hadoop/pull/1611



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to