[ https://issues.apache.org/jira/browse/HDFS-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087936#comment-16087936 ]
Bharat Viswanadham edited comment on HDFS-5896 at 7/14/17 8:03 PM: ------------------------------------------------------------------- Hi [~ikeda] Refer this JDK bug for setName/getName thread safe fix https://bugs.openjdk.java.net/browse/JDK-8010182 the methods setName and getName are synchronized and name is declared as volatile in Thread class. So, I think it will not be issue. was (Author: bharatviswa): Hi [~ikeda] Refer this JDK bug for setName/getName thread safe fix https://bugs.openjdk.java.net/browse/JDK-8010182 the methods setName and getName are synchronized from JDK 8. So, I think it will not be issue with JDK8. > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org