You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (Jira)" <ji...@apache.org> on 2019/09/04 15:50:00 UTC

[jira] [Resolved] (HBASE-22930) Set unique name to longCompactions/shortCompactions threads

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

stack resolved HBASE-22930.
---------------------------
    Fix Version/s: 2.2.2
                   2.1.7
                   2.3.0
                   3.0.0
     Hadoop Flags: Reviewed
       Resolution: Fixed

Merged to branch-2.1+. Thanks for the patch [~pankaj2461]

> 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
>             Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2
>
>
> 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)