[jira] [Created] (HBASE-26687) Account for HBASE-24500 in regionInfoMismatch tool

["Josh Elser (Jira)" <ji...@apache.org>]

Josh Elser created HBASE-26687:
----------------------------------

             Summary: Account for HBASE-24500 in regionInfoMismatch tool
                 Key: HBASE-26687
                 URL: https://issues.apache.org/jira/browse/HBASE-26687
             Project: HBase
          Issue Type: Bug
          Components: hbck2
            Reporter: Josh Elser
            Assignee: Josh Elser
             Fix For: hbase-operator-tools-1.3.0


Had a coworker try to use the RegionInfoMismatch tool I added in HBASE-26656. Curiously, the tool failed on the sanity check I added.
{noformat}
Aborting: sanity-check failed on updated RegionInfo. Expected encoded region name 736ee6186975de6967cd9e9e242423f0 but got 323748c77dde5b05982df0285b013232.
Incorrectly created RegionInfo was: {ENCODED => 323748c77dde5b05982df0285b013232, NAME => 'test4,,1642405560420_0002.323748c77dde5b05982df0285b013232.', STARTKEY => '', ENDKEY => ''}

{noformat}
I couldn't understand why the tool wasn't working until I hooked up a debugger and realized that the problem wasn't in my code :). The version of HBase on the system did not have the fix from HBASE-24500 included which meant that I was hitting the same "strange behavior", as Duo put it, in the RegionInfoBuilder "copy constructor".

While the versions of HBase which do not have this fix are EOL in terms of Apache releases, we can easily work around this in operator-tools (which may be used by any hbase 2.x release still in the wild).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)