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

ASF GitHub Bot logged work on HDFS-16634:
-----------------------------------------

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

   ### Description of PR
   On a busy cluster, sometimes it takes bit of time for deleted node(from the 
cluster)'s "slow node report" to get removed from slow peer json report on 
Namenode JMX metrics. In the meantime, user should be able to browse through 
more entries in the report by adjusting i.e. reconfiguring 
"dfs.datanode.max.nodes.to.report" so that the list size can be adjusted 
without user having to bounce active Namenode just for this purpose.
   
   ### How was this patch tested?
   Dev cluster and using 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: 782203)
    Remaining Estimate: 0h
            Time Spent: 10m

> Dynamically adjust slow peer report size on JMX metrics
> -------------------------------------------------------
>
>                 Key: HDFS-16634
>                 URL: https://issues.apache.org/jira/browse/HDFS-16634
>             Project: Hadoop HDFS
>          Issue Type: Task
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> On a busy cluster, sometimes it takes bit of time for deleted node(from the 
> cluster)'s "slow node report" to get removed from slow peer json report on 
> Namenode JMX metrics. In the meantime, user should be able to browse through 
> more entries in the report by adjusting i.e. reconfiguring 
> "dfs.datanode.max.nodes.to.report" so that the list size can be adjusted 
> without user having to bounce active Namenode just for this purpose.



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