anujmodi2021 opened a new pull request, #7837: URL: https://github.com/apache/hadoop/pull/7837
### Description of PR JIRA: https://issues.apache.org/jira/browse/HADOOP-19645 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: 1. Direct Read: Read from a given position in remote file. This will be synchronous read 2. Normal Read: Read from current seeked position where read ahead was bypassed. This will be synchronous read. 3. Prefetch Read: Read triggered from background threads filling up in memory cache. This will be asynchronous read. 4. Missed Cache Read: Read triggered after nothing was received from read ahead. This will be synchronous read. 5. Footer Read: Read triggered as part of footer read optimization. This will be synchronous. 6. 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. ### How was this patch tested? TBA -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
