[jira] [Commented] (HBASE-25146) Add extra logging at info level to HFileCorruptionChecker in order to report progress
[
https://issues.apache.org/jira/browse/HBASE-25146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209216#comment-17209216
]
Hudson commented on HBASE-25146:
Results for branch master
[build #84 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/84/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/84/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/84/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/84/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Add extra logging at info level to HFileCorruptionChecker in order to report
> progress
> -
>
> Key: HBASE-25146
> URL: https://issues.apache.org/jira/browse/HBASE-25146
> Project: HBase
> Issue Type: Improvement
> Components: hbck, hbck2
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> Currently there's no progress reporting in HFileCorruptionChecker: neither in
> the logs nor in stdout. It only creates a report about the entire operation
> at the end of the process and emits some warning messages is corruption is
> found.
> Adding some logging about the progress would be beneficial for long running
> checks indicating that the process is running healthy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-25146) Add extra logging at info level to HFileCorruptionChecker in order to report progress
[
https://issues.apache.org/jira/browse/HBASE-25146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209070#comment-17209070
]
Hudson commented on HBASE-25146:
Results for branch branch-2.2
[build #83 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/83//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Add extra logging at info level to HFileCorruptionChecker in order to report
> progress
> -
>
> Key: HBASE-25146
> URL: https://issues.apache.org/jira/browse/HBASE-25146
> Project: HBase
> Issue Type: Improvement
> Components: hbck, hbck2
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> Currently there's no progress reporting in HFileCorruptionChecker: neither in
> the logs nor in stdout. It only creates a report about the entire operation
> at the end of the process and emits some warning messages is corruption is
> found.
> Adding some logging about the progress would be beneficial for long running
> checks indicating that the process is running healthy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-25146) Add extra logging at info level to HFileCorruptionChecker in order to report progress
[
https://issues.apache.org/jira/browse/HBASE-25146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208715#comment-17208715
]
Hudson commented on HBASE-25146:
Results for branch branch-2
[build #70 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/70/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/70/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/70/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/70/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Add extra logging at info level to HFileCorruptionChecker in order to report
> progress
> -
>
> Key: HBASE-25146
> URL: https://issues.apache.org/jira/browse/HBASE-25146
> Project: HBase
> Issue Type: Improvement
> Components: hbck, hbck2
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> Currently there's no progress reporting in HFileCorruptionChecker: neither in
> the logs nor in stdout. It only creates a report about the entire operation
> at the end of the process and emits some warning messages is corruption is
> found.
> Adding some logging about the progress would be beneficial for long running
> checks indicating that the process is running healthy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-25146) Add extra logging at info level to HFileCorruptionChecker in order to report progress
[
https://issues.apache.org/jira/browse/HBASE-25146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208584#comment-17208584
]
Hudson commented on HBASE-25146:
Results for branch branch-2.3
[build #77 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/77/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/77/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/77/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/77/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/77//console].
> Add extra logging at info level to HFileCorruptionChecker in order to report
> progress
> -
>
> Key: HBASE-25146
> URL: https://issues.apache.org/jira/browse/HBASE-25146
> Project: HBase
> Issue Type: Improvement
> Components: hbck, hbck2
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> Currently there's no progress reporting in HFileCorruptionChecker: neither in
> the logs nor in stdout. It only creates a report about the entire operation
> at the end of the process and emits some warning messages is corruption is
> found.
> Adding some logging about the progress would be beneficial for long running
> checks indicating that the process is running healthy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-25146) Add extra logging at info level to HFileCorruptionChecker in order to report progress
[
https://issues.apache.org/jira/browse/HBASE-25146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207181#comment-17207181
]
Mate Szalay-Beko commented on HBASE-25146:
--
Also we just saw that the tool doesn't print out the number of mob files
checked. It is counting them with a different counter than the normal HFiles
({{hfilesChecked}}), but in the end it doesn't print out the value of the
{{mobFilesChecked}} counter. (I found this in 2.1, haven't check this on the
master branch)
> Add extra logging at info level to HFileCorruptionChecker in order to report
> progress
> -
>
> Key: HBASE-25146
> URL: https://issues.apache.org/jira/browse/HBASE-25146
> Project: HBase
> Issue Type: Improvement
> Components: hbck, hbck2
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
>
> Currently there's no progress reporting in HFileCorruptionChecker: neither in
> the logs nor in stdout. It only creates a report about the entire operation
> at the end of the process and emits some warning messages is corruption is
> found.
> Adding some logging about the progress would be beneficial for long running
> checks indicating that the process is running healthy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
