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 70404200CB8 for ; Sat, 17 Jun 2017 04:24:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6F1C5160BDD; Sat, 17 Jun 2017 02:24:05 +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 B5BEE160BEB for ; Sat, 17 Jun 2017 04:24:04 +0200 (CEST) Received: (qmail 17692 invoked by uid 500); 17 Jun 2017 02:24:03 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 17677 invoked by uid 99); 17 Jun 2017 02:24:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Jun 2017 02:24:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 64664C05CB for ; Sat, 17 Jun 2017 02:24:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id HVpLzbkzPhOq for ; Sat, 17 Jun 2017 02:24:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id F111F5F3FE for ; Sat, 17 Jun 2017 02:24:01 +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 BC411E0A2F for ; Sat, 17 Jun 2017 02:24:00 +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 1504524001 for ; Sat, 17 Jun 2017 02:24:00 +0000 (UTC) Date: Sat, 17 Jun 2017 02:24:00 +0000 (UTC) From: "Josh Elser (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17752) Update reporting RPCs/Shell commands to break out space utilization by snapshot MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 17 Jun 2017 02:24:05 -0000 [ https://issues.apache.org/jira/browse/HBASE-17752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052637#comment-16052637 ] Josh Elser commented on HBASE-17752: ------------------------------------ bq. Nit: Can we estimate the size of this map before construction? We can't. We're reading all of the serialized SpaceQuotaSnapshot objects for hbase snapshots in the hbase:quota table. Given the context we have, there could be zero or there could be 100's. Cleaned up the rest and added a little test case. 003 incoming shortly. > Update reporting RPCs/Shell commands to break out space utilization by snapshot > ------------------------------------------------------------------------------- > > Key: HBASE-17752 > URL: https://issues.apache.org/jira/browse/HBASE-17752 > Project: HBase > Issue Type: Sub-task > Reporter: Josh Elser > Assignee: Josh Elser > Attachments: HBASE-17752.001.patch, HBASE-17752.002.patch, HBASE-17752.003.patch > > > For adminstrators running HBase with space quotas, it is useful to provide a breakdown of the utilization of a table. For example, it may be non-intuitive that a table's utilization is primarily made up of snapshots. We should provide a new command or modify existing commands such that an admin can see the utilization for a table/ns: > e.g. > {noformat} > table1: 17GB > resident: 10GB > snapshot_a: 5GB > snapshot_b: 2GB > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029)