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

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

                Author: ASF GitHub Bot
            Created on: 22/Dec/21 14:01
            Start Date: 22/Dec/21 14:01
    Worklog Time Spent: 10m 
      Work Description: jianghuazhu opened a new pull request #3823:
URL: https://github.com/apache/hadoop/pull/3823


   
   ### Description of PR
   It looks like NNThroughputBenchmark#dummyActionNoSynch() has been deprecated 
and it should be deleted.
   
   ### How was this patch tested?
   For testing, there is not much pressure.
   
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

            Worklog Id:     (was: 700013)
    Remaining Estimate: 0h
            Time Spent: 10m

> Remove useless NNThroughputBenchmark#dummyActionNoSynch()
> ---------------------------------------------------------
>
>                 Key: HDFS-16395
>                 URL: https://issues.apache.org/jira/browse/HDFS-16395
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: benchmarks, namenode
>    Affects Versions: 2.9.2
>            Reporter: JiangHua Zhu
>            Assignee: JiangHua Zhu
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Doesn't seem to be used anywhere NNThroughputBenchmark#dummyActionNoSynch(), 
> It is recommended to delete it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to