From aee7379b7e7cc941ad1b22c9a0eda1a2593a455e Mon Sep 17 00:00:00 2001 From: Misty Stanley-Jones Date: Wed, 10 Sep 2014 08:04:37 +1000 Subject: [PATCH] HBASE-11909 Documented how to find the current number of regions and why the numbers in the UI might not agree with hbck output --- src/main/docbkx/ops_mgt.xml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/main/docbkx/ops_mgt.xml b/src/main/docbkx/ops_mgt.xml index 1d515f81323..19ff0cd5625 100644 --- a/src/main/docbkx/ops_mgt.xml +++ b/src/main/docbkx/ops_mgt.xml @@ -1578,6 +1578,17 @@ hbase> restore_snapshot 'myTableSnapshot-122112' xrefstyle="template:above" /> should be. So, if your data is compressed and replicated 3 ways by HDFS, "9 Gb region" means 9 Gb of compressed data. HDFS replication factor only affects your disk usage and is invisible to most HBase code. +
+ Viewing the Current Number of Regions + You can view the current number of regions for a given table using the HMaster UI. In + the Tables section, the number of online regions for each table is + listed in the Online Regions column. This total only includes the + in-memory state and does not include disabled or offline regions. If you do not want to + use the HMaster UI, you can determine the number of regions by counting the number of + subdirectories of the /hbase/<table>/ subdirectories in HDFS, or by running the + bin/hbase hbck command. Each of these methods may return a slightly + different number, depending on the status of each region. +
Number of regions per RS - upper bound