[ https://issues.apache.org/jira/browse/HDFS-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022499#comment-13022499 ]
Hudson commented on HDFS-1611: ------------------------------ Integrated in Hadoop-Hdfs-trunk #643 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk/643/]) > Some logical issues need to address. > ------------------------------------ > > Key: HDFS-1611 > URL: https://issues.apache.org/jira/browse/HDFS-1611 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs client, name-node > Affects Versions: 0.20.1, 0.20.2 > Reporter: Uma Maheswara Rao G > Assignee: Uma Maheswara Rao G > Priority: Minor > Fix For: 0.23.0 > > Attachments: HDFS-1611.1.patch, HDFS-1611.patch > > > Title: Some code level logical issues. > Description: > 1. DFSClient: > Consider the below case, if we enable only info, then below log will never > be logged. > if (ClientDatanodeProtocol.LOG.isDebugEnabled()) { > ClientDatanodeProtocol.LOG.info("ClientDatanodeProtocol addr=" + addr); > } > 2.org.apache.hadoop.hdfs.server.namenode.FSNamesystem.registerMBean() > > catch (NotCompliantMBeanException e) { > e.printStackTrace(); > } > We can avoid using stackTace(). Better to add log message. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira