[ 
https://issues.apache.org/jira/browse/HDFS-11558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937500#comment-15937500
 ] 

Tsz Wo Nicholas Sze commented on HDFS-11558:
--------------------------------------------

> I'd suggest the thread name be even shorter. ...

I agree.  Ideally, we only need
{code}
BP-948066398-XXXX-1490219911913 heartbeat to localhost/127.0.0.1:53014
{code}
However, the BP id may be missing in the beginning.  How about using the NS id 
if BP id is missing?  The NS id is available in 
BlockPoolManager.doRefreshNamenodes(..) but it is not passed down the road.

> BPServiceActor thread name is too long
> --------------------------------------
>
>                 Key: HDFS-11558
>                 URL: https://issues.apache.org/jira/browse/HDFS-11558
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Xiaobing Zhou
>            Priority: Minor
>         Attachments: HDFS-11558.000.patch, HDFS-11558.001.patch
>
>
> Currently, the thread name looks like
> {code}
> 2017-03-20 18:32:22,022 [DataNode: 
> [[[DISK]file:/Users/szetszwo/hadoop/t2/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/data/dn1_data0,
>  
> [DISK]file:/Users/szetszwo/hadoop/t2/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/data/dn1_data1]]
>   heartbeating to localhost/127.0.0.1:51772] INFO  ...
> {code}
> which contains the full path for each storage dir.  It is unnecessarily long.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to