From 77ac04efe46e4b374c3c6a20895ab7370b1206d3 Mon Sep 17 00:00:00 2001 From: Uma Maheswara Rao G Date: Fri, 22 Jul 2016 11:08:20 -0700 Subject: [PATCH] HDFS-10565: Erasure Coding: Document about the current allowed storage policies for EC Striped mode files --- .../hadoop-hdfs/src/site/markdown/ArchivalStorage.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/ArchivalStorage.md b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/ArchivalStorage.md index 803cc9171d..31bea7c77f 100644 --- a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/ArchivalStorage.md +++ b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/ArchivalStorage.md @@ -81,7 +81,9 @@ The following is a typical storage policy table. | 5 | Warm | DISK: 1, ARCHIVE: *n*-1 | ARCHIVE, DISK | ARCHIVE, DISK | | 2 | Cold | ARCHIVE: *n* | \ | \ | -Note that the Lazy\_Persist policy is useful only for single replica blocks. For blocks with more than one replicas, all the replicas will be written to DISK since writing only one of the replicas to RAM\_DISK does not improve the overall performance. +Note 1: The Lazy\_Persist policy is useful only for single replica blocks. For blocks with more than one replicas, all the replicas will be written to DISK since writing only one of the replicas to RAM\_DISK does not improve the overall performance. + +Note 2: For the erasure coded files with striping layout, the suitable storage policies are All\_SSD, Hot, Cold. So, if user sets the policy for striped EC files other than the mentioned policies, it will not follow that policy while creating or moving block. ### Storage Policy Resolution