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

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

anujmodi2021 commented on code in PR #8043:
URL: https://github.com/apache/hadoop/pull/8043#discussion_r2480654128


##########
hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azurebfs/services/AbfsRestOperation.java:
##########
@@ -453,7 +463,7 @@ private boolean executeHttpOperation(final int retryCount,
       }
         incrementCounter(AbfsStatistic.GET_RESPONSES, 1);
       //Only increment bytesReceived counter when the status code is 2XX.
-      if (httpOperation.getStatusCode() >= HttpURLConnection.HTTP_OK

Review Comment:
   Taken



##########
hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azurebfs/services/AbfsRestOperation.java:
##########
@@ -359,7 +369,7 @@ void completeExecute(TracingContext tracingContext)
   @VisibleForTesting
   void updateBackoffMetrics(int retryCount, int statusCode) {
     if (abfsBackoffMetrics != null) {
-      if (statusCode < HttpURLConnection.HTTP_OK

Review Comment:
   Taken



##########
hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azurebfs/services/ITestAbfsTailLatencyTracker.java:
##########
@@ -0,0 +1,75 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.hadoop.fs.azurebfs.services;
+
+import org.junit.jupiter.api.Test;
+
+import org.apache.hadoop.conf.Configuration;
+import org.apache.hadoop.fs.FileSystem;
+import org.apache.hadoop.fs.Path;
+import org.apache.hadoop.fs.azurebfs.AbstractAbfsIntegrationTest;
+import org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem;
+
+import static 
org.apache.hadoop.fs.azurebfs.constants.ConfigurationKeys.FS_AZURE_ENABLE_TAIL_LATENCY_REQUEST_TIMEOUT;
+import static 
org.apache.hadoop.fs.azurebfs.constants.ConfigurationKeys.FS_AZURE_ENABLE_TAIL_LATENCY_TRACKER;
+import static 
org.apache.hadoop.fs.azurebfs.constants.ConfigurationKeys.FS_AZURE_NETWORKING_LIBRARY;
+import static org.assertj.core.api.Assertions.assertThat;
+
+public class ITestAbfsTailLatencyTracker extends AbstractAbfsIntegrationTest {
+
+  protected ITestAbfsTailLatencyTracker() throws Exception {
+  }
+
+  @Test
+  public void testTailLatencyTimeoutEnabled() throws Exception {

Review Comment:
   Taken





> ABFS: [Perf] Network Profiling of Tailing Requests and Killing Bad 
> Connections Proactively
> ------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-19729
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19729
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 3.4.2
>            Reporter: Anuj Modi
>            Assignee: Anuj Modi
>            Priority: Major
>              Labels: pull-request-available
>
> It has been observed that certain requests taking more time than expected to 
> complete hinders the performance of whole workload. Such requests are known 
> as tailing requests. They can be taking more time due to a number of reasons 
> and the prominent among them is a bad network connection. In Abfs driver we 
> cache network connections and keeping such bad connections in cache and 
> reusing them can be bad for perf.
> In this effort we try to identify such connections and close them so that new 
> good connetions can be established and perf can be improved. There are two 
> parts of this effort.
>  # Identifying Tailing Requests: This involves profiling all the network 
> calls and getting percentiles value optimally. By default we consider p99 as 
> the tail latency and all the future requests taking more than tail latency 
> will be considere as Tailing requests.
>  # Proactively Killing Socket Connections: With Apache client, we can now 
> kill the socket connection and fail the tailing request. Such failures will 
> not be thrown back to user and retried immediately without any sleep but from 
> another socket connection.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to