Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D3412200D60 for ; Sat, 11 Nov 2017 03:22:08 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D1BAD160BEE; Sat, 11 Nov 2017 02:22:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 238C2160BF2 for ; Sat, 11 Nov 2017 03:22:07 +0100 (CET) Received: (qmail 93783 invoked by uid 500); 11 Nov 2017 02:22:07 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 93395 invoked by uid 99); 11 Nov 2017 02:22:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Nov 2017 02:22:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C8E5AD9B0C for ; Sat, 11 Nov 2017 02:22:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id eoBc3yPXKHQP for ; Sat, 11 Nov 2017 02:22:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 54FAB60DDB for ; Sat, 11 Nov 2017 02:22:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 188DAE0E4D for ; Sat, 11 Nov 2017 02:22:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id B770F240DA for ; Sat, 11 Nov 2017 02:22:01 +0000 (UTC) Date: Sat, 11 Nov 2017 02:22:01 +0000 (UTC) From: "Virajith Jalaparti (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-12775) [READ] Fix reporting of Provided volumes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 11 Nov 2017 02:22:09 -0000 [ https://issues.apache.org/jira/browse/HDFS-12775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Virajith Jalaparti updated HDFS-12775: -------------------------------------- Attachment: HDFS-12775-HDFS-9806.001.patch Posting a patch that reports the capacity of PROVIDED volumes as follows: #The capacity (and dfs used) of a PROVIDED volume on a DN is reported to be equal to the total size of the data (in bytes) mounted from the remote storage. Each volume reports zero available capacity (thus 100% usage). This included changes to {{ProvidedVolumeImpl}}, and adding a default {{ProvidedVolumeDF}} implementation and removing the earlier configurable {{ProvidedVolumeDF}} interface. # The capacity of the Provided volumes is not aggregated in the NN, and does not account towards the total capacity reported by the NN. Thus, the "Configured Capacity" metric reported in the NN Web UI only reports the local capacity available. # In stats reported by {{BlockStatsMXBean}}, the capacity of the PROVIDED storagetype is not aggregated across Datanodes. The reported capacity is equal to the capacity of the remote storage. # Adds a Provided capacity metric to JMX ({{getProvidedCapacity}} and to the NN web UI, to distinguish this capacity from that of the local HDFS capacity. These changes are motivated by the fact that the capacity of the PROVIDED volumes is virtual, and aggregating it across Datanodes in the Namenode can provide the illusion of having a capacity far greater than what is physically available in the cluster. > [READ] Fix reporting of Provided volumes > ---------------------------------------- > > Key: HDFS-12775 > URL: https://issues.apache.org/jira/browse/HDFS-12775 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Virajith Jalaparti > Assignee: Virajith Jalaparti > Attachments: HDFS-12775-HDFS-9806.001.patch > > > Provided Volumes currently report infinite capacity and 0 space used. Further, PROVIDED locations are reported as {{/default-rack/null:0}} in fsck. This JIRA is for making this more readable, and replace these with what users would expect. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org