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

Arpit Agarwal updated HADOOP-15772:
-----------------------------------
    Description: 
The following warnings are logged on service startup and are noise. It is 
perfectly valid to list local paths without using the URI syntax.
{code:java}
2018-09-16 23:16:11,393 WARN  common.Util (Util.java:stringAsURI(99)) - Path 
/hadoop/hdfs/namenode should be specified as a URI in configuration files. 
Please update hdfs configuration.{code}
 

  was:
The following warnings are logged multiple times on NameNode startup and are 
noise. It is perfectly valid to list local paths without using the URI syntax.
{code:java}
2018-09-16 23:16:11,393 WARN  common.Util (Util.java:stringAsURI(99)) - Path 
/hadoop/hdfs/namenode should be specified as a URI in configuration files. 
Please update hdfs configuration.{code}
 


> Remove the 'Path ... should be specified as a URI' warnings on startup
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-15772
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15772
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Arpit Agarwal
>            Assignee: Ayush Saxena
>            Priority: Major
>              Labels: newbie
>         Attachments: HDFS-13921-01.patch, HDFS-13921-02.patch
>
>
> The following warnings are logged on service startup and are noise. It is 
> perfectly valid to list local paths without using the URI syntax.
> {code:java}
> 2018-09-16 23:16:11,393 WARN  common.Util (Util.java:stringAsURI(99)) - Path 
> /hadoop/hdfs/namenode should be specified as a URI in configuration files. 
> Please update hdfs configuration.{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to