Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Fri, 25 Jan 2013 00:45:14 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12629171.1359067135317.188187.1359074714508@arcas>
In-Reply-To: <JIRA.12629171.1359067135317@arcas>
References: <JIRA.12629171.1359067135317@arcas>
Subject: [jira] [Resolved] (HDFS-4440) avoid annoying log message when
 dfs.domain.socket.path is not set
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers resolved HDFS-4440.
----------------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed

I've just committed this to the HDFS-347 branch. Thanks a lot for the contribution, Colin.
                
> avoid annoying log message when dfs.domain.socket.path is not set
> -----------------------------------------------------------------
>
>                 Key: HDFS-4440
>                 URL: https://issues.apache.org/jira/browse/HDFS-4440
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, hdfs-client, performance
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Trivial
>         Attachments: HDFS-4440.001.patch
>
>
> When dfs.domain.socket.path is not set, it gets set to the empty string.  We should check if this conf key is the empty string in {{DomainSocketFactory}}, rather than checking against null as we currently do.  Otherwise, we get annoying log messages about failing to connect to the UNIX domain socket at ''.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira