[jira] [Updated] (HDFS-16531) Avoid setReplication logging an edit record if old replication equals the new value

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-16531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HDFS-16531:
----------------------------------
    Labels: pull-request-available  (was: )

> Avoid setReplication logging an edit record if old replication equals the new value
> -----------------------------------------------------------------------------------
>
>                 Key: HDFS-16531
>                 URL: https://issues.apache.org/jira/browse/HDFS-16531
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> I recently came across a NN log where about 800k setRep calls were made, setting the replication from 3 to 3 - ie leaving it unchanged.
> Even in a case like this, we log an edit record, an audit log, and perform some quota checks etc.
> I believe it should be possible to avoid some of the work if we check for oldRep == newRep and jump out of the method early.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org