Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 430EB107D1 for ; Wed, 7 Jan 2015 03:12:35 +0000 (UTC) Received: (qmail 25145 invoked by uid 500); 7 Jan 2015 03:12:36 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 25096 invoked by uid 500); 7 Jan 2015 03:12:36 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 25066 invoked by uid 99); 7 Jan 2015 03:12:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2015 03:12:35 +0000 Date: Wed, 7 Jan 2015 03:12:35 +0000 (UTC) From: "Tsz Wo Nicholas Sze (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-7467) Provide storage tier information for a directory via fsck MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267222#comment-14267222 ] Tsz Wo Nicholas Sze commented on HDFS-7467: ------------------------------------------- > My recommendation is to display the policy along with the combination if possible. ... It is a good idea. We should also consider a file's specified storage policy and actually storage media. If a file does not satisfies the specified policy, fsck should show such information. E.g. the specified storage policy of file foo is hot but all the replicas are stored in ARCHIVE, then it should not be counted as "frozen". It should be counted as "ARCHIVE:3" in order to indicate that it does not satisfies the specified policy. > Provide storage tier information for a directory via fsck > --------------------------------------------------------- > > Key: HDFS-7467 > URL: https://issues.apache.org/jira/browse/HDFS-7467 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: balancer & mover > Affects Versions: 2.6.0 > Reporter: Benoy Antony > Assignee: Benoy Antony > Attachments: HDFS-7467.patch > > > Currently _fsck_ provides information regarding blocks for a directory. > It should be augmented to provide storage tier information (optionally). > The sample report could be as follows : > {code} > Storage Tier Combination # of blocks % of blocks > DISK:1,ARCHIVE:2 340730 97.7393% > > ARCHIVE:3 3928 1.1268% > > DISK:2,ARCHIVE:2 3122 0.8956% > > DISK:2,ARCHIVE:1 748 0.2146% > > DISK:1,ARCHIVE:3 44 0.0126% > > DISK:3,ARCHIVE:2 30 0.0086% > > DISK:3,ARCHIVE:1 9 0.0026% > {code} > -- This message was sent by Atlassian JIRA (v6.3.4#6332)