You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2019/11/01 01:38:00 UTC
[jira] [Commented] (HBASE-23192) CatalogJanitor consistencyCheck
does not log problematic row on exception
[ https://issues.apache.org/jira/browse/HBASE-23192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964507#comment-16964507 ]
Hudson commented on HBASE-23192:
--------------------------------
Results for branch branch-2.2
[build #679 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/679/]: (x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/679//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/679//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/679//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> CatalogJanitor consistencyCheck does not log problematic row on exception
> -------------------------------------------------------------------------
>
> Key: HBASE-23192
> URL: https://issues.apache.org/jira/browse/HBASE-23192
> Project: HBase
> Issue Type: Bug
> Components: hbck2
> Affects Versions: 2.1.7, 2.2.2
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.3.3
>
>
> Small stuff. Trying to fix a cluser, cleared an info:server field. Damaged hbase:meta for CatalogJanitor; when it should have just logged and skipped the bad entity when doing consistency check, instead CJ crashed. Also doesn't log bad raw which would help debugging.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)