-
Type:
Sub-task
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.0.0-alpha-1, 2.3.0
-
Component/s: wal
-
Labels:None
-
Hadoop Flags:Reviewed
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...
... 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. ...
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.
- is related to
-
HBASE-24585 Failed start recovering crash in standalone mode if procedure-based distributed WAL split & hbase.wal.split.to.hfile=true
-
- Resolved
-
- links to