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

ASF GitHub Bot commented on HADOOP-19645:
-----------------------------------------

anujmodi2021 commented on PR #7837:
URL: https://github.com/apache/hadoop/pull/7837#issuecomment-3135851673

   -----------------------------
   :::: AGGREGATED TEST RESULT ::::
   
   ============================================================
   HNS-OAuth-DFS
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 3
   [WARNING] Tests run: 874, Failures: 0, Errors: 0, Skipped: 223
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 34
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 23
   
   ============================================================
   HNS-SharedKey-DFS
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 4
   [WARNING] Tests run: 874, Failures: 0, Errors: 0, Skipped: 172
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 34
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 10
   
   ============================================================
   NonHNS-SharedKey-DFS
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 10
   [WARNING] Tests run: 858, Failures: 0, Errors: 0, Skipped: 395
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 35
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 11
   
   ============================================================
   AppendBlob-HNS-OAuth-DFS
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 3
   [WARNING] Tests run: 874, Failures: 0, Errors: 0, Skipped: 234
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 58
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 23
   
   ============================================================
   NonHNS-SharedKey-Blob
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 10
   [WARNING] Tests run: 858, Failures: 0, Errors: 0, Skipped: 285
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 29
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 11
   
   ============================================================
   NonHNS-OAuth-DFS
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 10
   [WARNING] Tests run: 858, Failures: 0, Errors: 0, Skipped: 400
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 35
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 24
   
   ============================================================
   NonHNS-OAuth-Blob
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 10
   [WARNING] Tests run: 858, Failures: 0, Errors: 0, Skipped: 301
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 29
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 24
   
   ============================================================
   AppendBlob-NonHNS-OAuth-Blob
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 10
   [WARNING] Tests run: 858, Failures: 0, Errors: 0, Skipped: 346
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 53
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 24
   
   ============================================================
   HNS-Oauth-DFS-IngressBlob
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 3
   [WARNING] Tests run: 874, Failures: 0, Errors: 0, Skipped: 356
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 34
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 23
   
   ============================================================
   NonHNS-OAuth-DFS-IngressBlob
   ============================================================
   
   [WARNING] Tests run: 177, Failures: 0, Errors: 0, Skipped: 10
   [WARNING] Tests run: 858, Failures: 0, Errors: 0, Skipped: 397
   [WARNING] Tests run: 182, Failures: 0, Errors: 0, Skipped: 35
   [WARNING] Tests run: 269, Failures: 0, Errors: 0, Skipped: 24
   
   




> ABFS: [ReadAheadV2] Improve Metrics for Read Calls to identify type of read 
> done.
> ---------------------------------------------------------------------------------
>
>                 Key: HADOOP-19645
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19645
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 3.3.6, 3.4.1
>            Reporter: Anuj Modi
>            Assignee: Anuj Modi
>            Priority: Major
>              Labels: pull-request-available
>
> There are a number of ways in which ABFS driver can trigger a network call to 
> read data. We need a way to identify what type of read call was made from 
> client. Plan is to add an indication for this in already present 
> ClientRequestId header.
> Following are types of read we want to identify:
>  # Direct Read: Read from a given position in remote file. This will be 
> synchronous read
>  # Normal Read: Read from current seeked position where read ahead was 
> bypassed. This will be synchronous read.
>  # Prefetch Read: Read triggered from background threads filling up in memory 
> cache. This will be asynchronous read.
>  # Missed Cache Read: Read triggered after nothing was received from read 
> ahead. This will be synchronous read.
>  # Footer Read: Read triggered as part of footer read optimization. This will 
> be synchronous.
>  # Small File Read: Read triggered as a part of small file read. This will be 
> synchronous read.
> We will add another field in the Tracing Header (Client Request Id) for each 
> request. We can call this field "Operation Specific Header" very similar to 
> how we have "Retry Header" today. As part of this we will only use it for 
> read operations keeping it empty for other operations. Moving ahead f we need 
> to publish any operation specific info, same header can be used.



--
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

Reply via email to