[
https://issues.apache.org/jira/browse/HBASE-22930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pankaj Kumar updated HBASE-22930:
---------------------------------
Description:
Sometime observed multiple compaction threads have the same name which is
misleading while analysing the log.
Currently we just append the current timestamp which can be same for multiple
threads,
[https://github.com/apache/hbase/blob/ec68bf30ba91ea7484d3b56b0809ff5434f9406e/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplit.java#L144]
was:
Sometime I observed multiple compaction threads have the same name which is
misleading while analysing the log.
Currently we just append the current timestamp which can be same for multiple
threads,
https://github.com/apache/hbase/blob/ec68bf30ba91ea7484d3b56b0809ff5434f9406e/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplit.java#L144
> Set unique name to longCompactions/shortCompactions threads
> -----------------------------------------------------------
>
> Key: HBASE-22930
> URL: https://issues.apache.org/jira/browse/HBASE-22930
> Project: HBase
> Issue Type: Improvement
> Reporter: Pankaj Kumar
> Assignee: Pankaj Kumar
> Priority: Minor
>
> Sometime observed multiple compaction threads have the same name which is
> misleading while analysing the log.
> Currently we just append the current timestamp which can be same for multiple
> threads,
> [https://github.com/apache/hbase/blob/ec68bf30ba91ea7484d3b56b0809ff5434f9406e/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplit.java#L144]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
