Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 4 Jan 2017 15:12:58 +0000 (UTC)
From: "Surendra Singh Lilhore (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.13031988.1483542735000.639370.1483542778848@Atlassian.JIRA>
In-Reply-To: <JIRA.13031988.1483542735000@Atlassian.JIRA>
References: <JIRA.13031988.1483542735000@Atlassian.JIRA> <JIRA.13031988.1483542735331@arcas>
Subject: [jira] [Created] (HDFS-11291) Avoid unnecessary edit log for
 setStoragePolicy() and setReplication()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 04 Jan 2017 15:13:00 -0000

Surendra Singh Lilhore created HDFS-11291:
---------------------------------------------

             Summary: 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


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.4#6332)

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