[ 
https://issues.apache.org/jira/browse/HADOOP-18288?focusedWorklogId=782509&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-782509
 ]

ASF GitHub Bot logged work on HADOOP-18288:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Jun/22 18:43
            Start Date: 17/Jun/22 18:43
    Worklog Time Spent: 10m 
      Work Description: steveloughran commented on code in PR #4431:
URL: https://github.com/apache/hadoop/pull/4431#discussion_r900425047


##########
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestConsistentReadsObserver.java:
##########
@@ -123,7 +123,7 @@ public void testRequeueCall() throws Exception {
         + CommonConfigurationKeys.IPC_BACKOFF_ENABLE, true);
 
     NameNodeAdapter.getRpcServer(nn).refreshCallQueue(configuration);
-    assertEquals(1, NameNodeAdapter.getRpcServer(nn).getTotalRequests());
+    assertTrue(NameNodeAdapter.getRpcServer(nn).getTotalRequests() > 0);

Review Comment:
   thanks! it is pretty verbose for the little things, but i find assertj 
lovely for complex things, especially collections





Issue Time Tracking
-------------------

    Worklog Id:     (was: 782509)
    Time Spent: 2h 20m  (was: 2h 10m)

> Total requests and total requests per sec served by RPC servers
> ---------------------------------------------------------------
>
>                 Key: HADOOP-18288
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18288
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> RPC Servers provide bunch of useful information like num of open connections, 
> slow requests, num of in-progress handlers, RPC processing time, queue time 
> etc, however so far it doesn't provide accumulation of all requests as well 
> as current snapshot of requests per second served by the server. Exposing 
> them would benefit from operational viewpoint in identifying how busy the 
> servers have been and how much load they are currently serving in the 
> presence of cluster wide high load.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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