hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiroshi Ikeda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5896) DataXceiver and DFSOutputStream call Thread.setName(), which is not thread safe
Date Tue, 18 Jul 2017 00:28:00 GMT

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

Hiroshi Ikeda commented on HDFS-5896:
-------------------------------------

Sorry I've left from Java for so long and I've forgotten many things.
I still feel that fix is a little ad-hoc but it seems enough to ensure its visibility.
I don't have source codes at hand but I feel it seems OK :)

> DataXceiver and DFSOutputStream call Thread.setName(), which is not thread safe
> -------------------------------------------------------------------------------
>
>                 Key: HDFS-5896
>                 URL: https://issues.apache.org/jira/browse/HDFS-5896
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Hiroshi Ikeda
>            Assignee: Bharat Viswanadham
>            Priority: Trivial
>
> org.apache.hadoop.hdfs.server.datanode.DataXceiver and org.apache.hadoop.hdfs.DFSOutputStream
renames running threads, but Thread.setName() is not thread safe. Thread.setName() is currently
intended to call before running the thread.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message