From b458fc7d9cde19748d0689baf4f66b1db7c4c306 Mon Sep 17 00:00:00 2001 From: Andrew Wang Date: Mon, 11 Nov 2013 19:24:44 +0000 Subject: [PATCH] HDFS-5467. Remove tab characters in hdfs-default.xml. Contributed by Shinichi Yamashita. git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/branch-2@1540815 13f79535-47bb-0310-9956-ffa450edef68 --- hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt | 4 ++ .../src/main/resources/hdfs-default.xml | 62 +++++++++---------- 2 files changed, 35 insertions(+), 31 deletions(-) diff --git a/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt b/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt index b30f273c127..32c42eb8921 100644 --- a/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt +++ b/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt @@ -99,6 +99,9 @@ Release 2.3.0 - UNRELEASED HDFS-5371. Let client retry the same NN when "dfs.client.test.drop.namenode.response.number" is enabled. (jing9) + HDFS-5467. Remove tab characters in hdfs-default.xml. + (Shinichi Yamashita via Andrew Wang) + OPTIMIZATIONS HDFS-5239. Allow FSNamesystem lock fairness to be configurable (daryn) @@ -107,6 +110,7 @@ Release 2.3.0 - UNRELEASED (Qus-Jiawei via kihwal) BUG FIXES + HDFS-5034. Remove debug prints from GetFileLinkInfo (Andrew Wang via Colin Patrick McCabe) diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml b/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml index 7685f094338..40817c19734 100644 --- a/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml +++ b/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml @@ -1393,43 +1393,43 @@ - dfs.namenode.enable.retrycache - true - - This enables the retry cache on the namenode. Namenode tracks for - non-idempotent requests the corresponding response. If a client retries the - request, the response from the retry cache is sent. Such operations - are tagged with annotation @AtMostOnce in namenode protocols. It is - recommended that this flag be set to true. Setting it to false, will result - in clients getting failure responses to retried request. This flag must - be enabled in HA setup for transparent fail-overs. - - The entries in the cache have expiration time configurable - using dfs.namenode.retrycache.expirytime.millis. - + dfs.namenode.enable.retrycache + true + + This enables the retry cache on the namenode. Namenode tracks for + non-idempotent requests the corresponding response. If a client retries the + request, the response from the retry cache is sent. Such operations + are tagged with annotation @AtMostOnce in namenode protocols. It is + recommended that this flag be set to true. Setting it to false, will result + in clients getting failure responses to retried request. This flag must + be enabled in HA setup for transparent fail-overs. + + The entries in the cache have expiration time configurable + using dfs.namenode.retrycache.expirytime.millis. + - dfs.namenode.retrycache.expirytime.millis - 600000 - - The time for which retry cache entries are retained. - + dfs.namenode.retrycache.expirytime.millis + 600000 + + The time for which retry cache entries are retained. + - dfs.namenode.retrycache.heap.percent - 0.03f - - This parameter configures the heap size allocated for retry cache - (excluding the response cached). This corresponds to approximately - 4096 entries for every 64MB of namenode process java heap size. - Assuming retry cache entry expiration time (configured using - dfs.namenode.retrycache.expirytime.millis) of 10 minutes, this - enables retry cache to support 7 operations per second sustained - for 10 minutes. As the heap size is increased, the operation rate - linearly increases. - + dfs.namenode.retrycache.heap.percent + 0.03f + + This parameter configures the heap size allocated for retry cache + (excluding the response cached). This corresponds to approximately + 4096 entries for every 64MB of namenode process java heap size. + Assuming retry cache entry expiration time (configured using + dfs.namenode.retrycache.expirytime.millis) of 10 minutes, this + enables retry cache to support 7 operations per second sustained + for 10 minutes. As the heap size is increased, the operation rate + linearly increases. +