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

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

                Author: ASF GitHub Bot
            Created on: 12/Jun/22 01:26
            Start Date: 12/Jun/22 01:26
    Worklog Time Spent: 10m 
      Work Description: virajjasani opened a new pull request, #4431:
URL: https://github.com/apache/hadoop/pull/4431

   ### Description of PR
   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.
   
   ### How was this patch tested?
   Local dev cluster and UT.
   
   ### For code changes:
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   




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

            Worklog Id:     (was: 780572)
    Remaining Estimate: 0h
            Time Spent: 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
>          Time Spent: 10m
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to