You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "hemanthboyina (Jira)" <ji...@apache.org> on 2019/08/28 17:03:00 UTC

[jira] [Updated] (HDFS-11291) Avoid unnecessary edit log for setStoragePolicy() and setReplication()

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

hemanthboyina updated HDFS-11291:
---------------------------------
    Attachment: HDFS-11291.003.patch

> Avoid unnecessary edit log for setStoragePolicy() and setReplication()
> ----------------------------------------------------------------------
>
>                 Key: HDFS-11291
>                 URL: https://issues.apache.org/jira/browse/HDFS-11291
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Surendra Singh Lilhore
>            Assignee: hemanthboyina
>            Priority: Major
>         Attachments: HDFS-11291.001.patch, HDFS-11291.002.patch, HDFS-11291.003.patch
>
>
> We are setting the storage policy for file without checking the current policy of file for avoiding extra getStoragePolicy() rpc call. Currently namenode is not checking the current storage policy before setting new one and adding edit logs. I think if the old and new storage policy is same we can avoid set operation.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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