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

[jira] [Resolved] (HBASE-23332) [HBCKReport] Split Regions shown as Overlaps in 'Overlap' section

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

Michael Stack resolved HBASE-23332.
-----------------------------------
    Resolution: Cannot Reproduce

Resolving. Lost logs. Seems like root cause is corrupt procedure. Spent time verifying we don't drop 'split/offline' flags when serializing to hbase:meta and that seems fine. Resolving because unable to debug.

> [HBCKReport] Split Regions shown as Overlaps in 'Overlap' section
> -----------------------------------------------------------------
>
>                 Key: HBASE-23332
>                 URL: https://issues.apache.org/jira/browse/HBASE-23332
>             Project: HBase
>          Issue Type: Bug
>          Components: hbck2, UI
>            Reporter: Michael Stack
>            Priority: Major
>
> The new 'HBCK Report' page has to be exacting else makes for wild goose chase or worse, operator damage of running cluster.
> I just came across instances where split parents as reported as overlapping their daughters:
> {code}
>  {ENCODED => 22776817918e40d0ba93eb48314d65a1, NAME => 't1,2ac082e1,1572669261019.22776817918e40d0ba93eb48314d65a1.', STARTKEY => '2ac082e1', ENDKEY => '2b020c18'}  {ENCODED => 8cbe15b2f59d69974357e8800a0bfbbc, NAME => 't1,2ac082e1,1574362260851.8cbe15b2f59d69974357e8800a0bfbbc.', STARTKEY => '2ac082e1', ENDKEY => '2ae3529d-1d72-4250-9bd8-4e9b9959284f'}
>  {ENCODED => 22776817918e40d0ba93eb48314d65a1, NAME => 't1,2ac082e1,1572669261019.22776817918e40d0ba93eb48314d65a1.', STARTKEY => '2ac082e1', ENDKEY => '2b020c18'}  {ENCODED => bd062ce8e9c99a6988f0a8223168e028, NAME => 't1,2ae3529d-1d72-4250-9bd8-4e9b9959284f,1574362260851.bd062ce8e9c99a6988f0a8223168e028.', STARTKEY => '2ae3529d-1d72-4250-9bd8-            4e9b9959284f', ENDKEY => '2b020c18'}
> {code}
> Need to fix.



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