Glad to hear! ... View more

Many thanks for following up! I do think the directory-or-file can be checked for before traversal, or at least the error message may be improved, for which I've filed https://issues.apache.org/jira/browse/HDFS-5802. The shell utils handle this in a clearer way btw: ➜ ~ ls foo/file ls: foo/file: Not a directory ➜ ~ hadoop fs -ls foo/file ls: `foobar/file': No such file or directory ... View more

Thanks for the information.   Regards ... View more

Ok great. I restarted all MapReduce and Hbase daemons in addition to the HDFS daemons and it is working properly now. Thank you!   Previously I had only restarted HDFS. ... View more

Hi, many thanks for your explanation. I'll check out the custom sink wrapper stuff... ... View more

Thanks Harsh   I will try to find out from eclipse project settings if it refers to localjobrunner somewhere in it, any further information from your end will be appreacited.   Regards ... View more

@herdrick: no it's actually just fine to do it in the order Harsh mentioned.  CM will automatically deploy the configurations you specify on the Configuration tab of a service to that service's roles when you restart the service.  For example, if you modify a datanode specific property in CM, save the change and restart the service, then all the datanodes will get new copies of their hdfs-site.xml files upon startup.  The only reason to deploy the client configs that Harsh mentioned is for external client apps that want to utilize the cluster.  If you made changes that will affect the behavior of clients, then the client configs need to be re-deployed.  This can happen after the services are restarted, but before you attempt to reconnect to the cluster with your client app.  I hope that clears it up.   Clint ... View more