[
https://issues.apache.org/jira/browse/HBASE-24574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140185#comment-17140185
]
Hudson commented on HBASE-24574:
--------------------------------
Results for branch branch-2
[build #2710 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2710/]:
(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/2710/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2710/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2710/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2710/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}
> Procedure V2 - Distributed WAL Splitting => LOGGING
> ---------------------------------------------------
>
> Key: HBASE-24574
> URL: https://issues.apache.org/jira/browse/HBASE-24574
> Project: HBase
> Issue Type: Sub-task
> Components: wal
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.1
>
>
> The procedure-based distributed WAL splitter uses the old SplitLogManager
> class. It registers it as a chore even though the chore #run immediately
> skips out. Meantime we log SLM ran in #0ms frequently. For example...
> {code}
> ...
> 2020-06-17 17:48:30,567 DEBUG [localhost:16000.splitLogManager..Chore.1]
> hbase.ScheduledChore: SplitLogManager Timeout Monitor execution time: 0 ms.
> 2020-06-17 17:48:31,567 DEBUG [localhost:16000.splitLogManager..Chore.1]
> hbase.ScheduledChore: SplitLogManager Timeout Monitor execution time: 0 ms.
> 2020-06-17 17:48:32,570 DEBUG [localhost:16000.splitLogManager..Chore.1]
> hbase.ScheduledChore: SplitLogManager Timeout Monitor execution time: 0 ms.
> 2020-06-17 17:48:33,567 DEBUG [localhost:16000.splitLogManager..Chore.1]
> hbase.ScheduledChore: SplitLogManager Timeout Monitor execution time: 0 ms.
> 2020-06-17 17:48:34,569 DEBUG [localhost:16000.splitLogManager..Chore.1]
> hbase.ScheduledChore: SplitLogManager Timeout Monitor execution time: 0 ms.
> 2020-06-17 17:48:35,569 DEBUG [localhost:16000.splitLogManager..Chore.1]
> hbase.ScheduledChore: SplitLogManager Timeout Monitor execution time: 0 ms.
> 2020-06-17 17:48:36,568 DEBUG [localhost:16000.splitLogManager..Chore.1]
> hbase.ScheduledChore: SplitLogManager Timeout Monitor execution time: 0 ms.
> ...
> {code}
> The new pv2 WAL splitter introduces new procedures that log their class name
> only w/o detail on log that is being split or the server that is running the
> split.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
