hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Surendra Singh Lilhore (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11291) Avoid unnecessary edit log for setStoragePolicy() and setReplication()
Date Sun, 16 Apr 2017 07:11:41 GMT

    [ https://issues.apache.org/jira/browse/HDFS-11291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970260#comment-15970260
] 

Surendra Singh Lilhore commented on HDFS-11291:
-----------------------------------------------

Thanks [~vinayrpet],

bq. Also I have doubt whether its correct to log audit when there is no change done and no
edit txn added.

Hi [~arpitagarwal], Can you give your view on this ?

> 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: Surendra Singh Lilhore
>         Attachments: HDFS-11291.001.patch, HDFS-11291.002.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
(v6.3.15#6346)

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


Mime
View raw message