You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2019/12/10 04:26:00 UTC

[jira] [Updated] (HBASE-23554) Encoded regionname to regionname utility

     [ https://issues.apache.org/jira/browse/HBASE-23554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Stack updated HBASE-23554:
----------------------------------
    Release Note: 
    Adds shell command regioninfo:

      hbase(main):001:0>  regioninfo '0e6aa5c19ae2b2627649dc7708ce27d0'
      {ENCODED => 0e6aa5c19ae2b2627649dc7708ce27d0, NAME => 'TestTable,,1575941375972.0e6aa5c19ae2b2627649dc7708ce27d0.', STARTKEY => '', ENDKEY => '00000000000000000000299441'}
      Took 0.4737 seconds

> Encoded regionname to regionname utility
> ----------------------------------------
>
>                 Key: HBASE-23554
>                 URL: https://issues.apache.org/jira/browse/HBASE-23554
>             Project: HBase
>          Issue Type: Bug
>          Components: shell
>            Reporter: Michael Stack
>            Assignee: Michael Stack
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0, 2.2.3
>
>
> Debugging I keep wanting to look at region state/transition in meta but all I have is encoded region name gleaned from log or from some parts of the UI. I find myself doing dump of the meta table to a text file just to search especially if region replicas are enabled (their encoded name is not even mentioned in hbase:meta). Utility that let me lookup regionname using encoded regionname would be handy.
> This actually exists already... almost. The Admin Service has a getRegionInfo. Usually it just returns RegionInfo if passed a region name. It can add a bit more info if it a MOB Region and the query is against Master or if the query is against the hosting RegionServer, it can tack on some compaction state detail. Wouldn't take much to extend this existing facility so could query w/ encoded name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)