[ 
https://issues.apache.org/jira/browse/HBASE-26525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaolin Ha updated HBASE-26525:
-------------------------------
    Description: 
The consumer threads for each WAL group has the same names, since they only 
uses 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 name 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.

 

  was:
The consumer threads for each WAL group has the same names, since they only 
uses 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 name 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-01-16-21-18-032.png|width=852,height=153!

So we can clearly see what happens from the log and the jstack info if 
something wrong with the WAL.

 


> 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
>         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 names, since they only 
> uses 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 name 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.1#820001)

Reply via email to