[
https://issues.apache.org/jira/browse/HBASE-26525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848096#comment-17848096
]
Duo Zhang commented on HBASE-26525:
-----------------------------------
We missed the commit on branch-2 in the past so we need to reset the fix
versions.
Thanks [~szucsvillo] for helping!
> Use unique thread name for group WALs
> -------------------------------------
>
> Key: HBASE-26525
> URL: https://issues.apache.org/jira/browse/HBASE-26525
> Project: HBase
> Issue Type: Improvement
> Components: wal
> Affects Versions: 3.0.0-alpha-1, 2.0.0
> Reporter: Xiaolin Ha
> Assignee: Xiaolin Ha
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0-alpha-2, 2.4.9, 2.7.0, 2.6.1, 2.5.9
>
> Attachments: image-2021-12-01-16-20-18-912.png,
> image-2021-12-01-16-21-18-032.png, image-2021-12-02-17-38-21-959.png
>
>
> The consumer threads for each WAL group has the same name, since they only
> use the WAL root dir in the thread name.
> {code:java}
> new ThreadFactoryBuilder().setNameFormat("AsyncFSWAL-%d-" +
> rootDir.toString()).
> setDaemon(true).build()); {code}
> For example, for BoundedGroupingStrategy, the consumer threads names are as
> follows,
> !image-2021-12-01-16-20-18-912.png|width=1199,height=130!
> We can use the log prefix instead, the consumer threads names will be changed
> to
> !image-2021-12-02-17-38-21-959.png|width=1102,height=197!
> So we can clearly see what happens from the log and the jstack info if
> something wrong with the WAL.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
