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 2BB99200CC7 for ; Sun, 16 Jul 2017 20:31:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2337F1641E5; Sun, 16 Jul 2017 18:31: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 6593B1641E4 for ; Sun, 16 Jul 2017 20:31:07 +0200 (CEST) Received: (qmail 79075 invoked by uid 500); 16 Jul 2017 18:31:05 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 79064 invoked by uid 99); 16 Jul 2017 18:31:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Jul 2017 18:31:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5C0B21A0409 for ; Sun, 16 Jul 2017 18:31:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id zWo5VFP5TuCO for ; Sun, 16 Jul 2017 18:31: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 01DD15F3BC for ; Sun, 16 Jul 2017 18:31: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 D235CE07D3 for ; Sun, 16 Jul 2017 18:31:02 +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 497462475D for ; Sun, 16 Jul 2017 18:31:01 +0000 (UTC) Date: Sun, 16 Jul 2017 18:31:01 +0000 (UTC) From: "Lars George (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References:

Subject: [jira] [Created] (HBASE-18388) Fix description on region page, explaining what a region name is made of MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 16 Jul 2017 18:31:08 -0000 Lars George created HBASE-18388: ----------------------------------- Summary: Fix description on region page, explaining what a region name is made of Key: HBASE-18388 URL: https://issues.apache.org/jira/browse/HBASE-18388 Project: HBase Issue Type: Improvement Components: master, regionserver, UI Affects Versions: 2.0.0-alpha-1, 1.3.1 Reporter: Lars George Priority: Minor In the {{RegionListTmpl.jamon}} we have this: {code}

Region names are made of the containing table's name, a comma, the start key, a comma, and a randomly generated region id. To illustrate, the region named domains,apache.org,5464829424211263407 is party to the table domains, has an id of 5464829424211263407 and the first key in the region is apache.org. The hbase:meta 'table' is an internal system table (or a 'catalog' table in db-speak). The hbase:meta table keeps a list of all regions in the system. The empty key is used to denote table start and table end. A region with an empty start key is the first region in a table. If a region has both an empty start key and an empty end key, it's the only region in the table. See HBase Home for further explication.

{code} This is wrong and worded oddly. What needs to be fixed facts wise is: - Region names contain (separated by commas) the full table name (including the namespace), the start key, the time the region was created, and finally a dot with an MD5 hash of everything before the dot. For example: {{test,,1499410125885.1544f69aeaf787755caa11d3567a9621.}} - The trailing dot is to distinguish legacy region names (like those used by the {{hbase:meta}} table) - The MD5 hash is used as the directory name within the HBase storage directories - The names for the meta table use a Jenkins hash instead, also leaving out the trailing dot, for example {{hbase:meta,,1.1588230740}}. The time is always set to {{1}}. - The start key is printed in safe characters, escaping unprintable characters - The link to the HBase home page to explain more is useless and should be removed. - Also, for region replicas, the replica ID is inserted into the name, like so {{replicatable,,1486289678486_0001.3e8b7655299b21b3038ff8d39062467f.}}, see the {{_0001}} part. As for the wording, I would just make this all flow a little better, that "is party of" sounds weird to me (IMHO). -- This message was sent by Atlassian JIRA (v6.4.14#64029)