Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-23554

Encoded regionname to regionname utility

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0-alpha-1, 2.3.0, 2.2.3, 2.1.9
    • shell
    • None
    • Reviewed
    • Hide
          Adds shell command regioninfo:

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

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              stack Michael Stack
              stack Michael Stack
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: