You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/06/18 00:50:00 UTC
[jira] [Updated] (HBASE-24574) Procedure V2 - Distributed WAL
Splitting => LOGGING
[ https://issues.apache.org/jira/browse/HBASE-24574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Stack updated HBASE-24574:
----------------------------------
Description:
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.
was:
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.
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.
> 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
>
> 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)