Uh oh!
There was an error while loading. Please reload this page.
HBASE-27560 fix consistencyCheck did not report the hole on last region - #4950
Conversation
Apache-HBase
commented
Jan 9, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 9, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 9, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 10, 2023
🎊 +1 overall
This message was automatically generated. |
Apache9
commented
Jan 10, 2023
So the problem here is that, if the table is disabled, we will skip checking but in the old code, we will still record the previous region info, so the check for the previous table's last region will be skipped? The fix here is to not record the previous region for disabled table? What if there are only two tables, one is enabled and we check it first, the other is disabled? Do we still have chance to check the last region for the enabled table? |
Apache-HBase
commented
Jan 10, 2023
🎊 +1 overall
This message was automatically generated. |
liuzhongjun89
commented
Jan 10, 2023
Think you for review, Exactly as you said, The old code just lose previous region info when the next table is disabled. In the scenario you mentioned, ReportMakingVisitor will keep the previous region info and check it on visitor close, just like it is the last table
|
Apache-HBase
commented
Jan 11, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 11, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 11, 2023
🎊 +1 overall
This message was automatically generated. |
…on (apache#4950) Signed-off-by: Duo Zhang <zhangduo@apache.org> (cherry picked from commit c1b9d8b) (cherry picked from commit 56ebf93) Change-Id: I7b604e9e2ac66866ddec0856df4dddb2c58941bd
No description provided.