[
https://issues.apache.org/jira/browse/HDFS-16531?focusedWorklogId=757660&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-757660
]
ASF GitHub Bot logged work on HDFS-16531:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Apr/22 12:07
Start Date: 17/Apr/22 12:07
Worklog Time Spent: 10m
Work Description: Hexiaoqiao commented on PR #4148:
URL: https://github.com/apache/hadoop/pull/4148#issuecomment-1100862879
Committed to trunk. Thanks @sodonnel for your contributions and thanks
@jojochuang, @hemanthboyina for your coments.
@sodonnel Please feel free to cherry-pick to other active branches or let me
know if we need backport. Thanks again.
Issue Time Tracking
-------------------
Worklog Id: (was: 757660)
Time Spent: 1h 20m (was: 1h 10m)
> 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: 1h 20m
> 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: [email protected]
For additional commands, e-mail: [email protected]
