Re: Datanode can't connect namenode with kerberos

The problem seem to be here, when I start datanode, the dnUser here is datanode other than the user start it, does anyone know how to determine the user? 2018-11-09 17:25:00,706 INFO org.apache.hadoop.http.HttpServer2: Jetty bound to port 50475 815960 2018-11-09 17:25:00,706 INFO org.mortbay.lo

Re: Datanode can't connect namenode with kerberos

And another wired thing, when I try mkdir in hdfs, it show the following error, $hadoop dfs -mkdir /user DEPRECATED: Use of this script to execute hdfs command is deprecated. Instead use the hdfs command for it. mkdir: Permission denied: user=kousouda, access=WRITE, inode="/":namenode:supergroup:

Re: Datanode can't connect namenode with kerberos

I run all process with the same user. And it should be the superuser since it start the namenode, is there some configuration I need to do to let the datanode become superuser? > On 9 Nov 2018, at 3:37 PM, Attila Bukor > wrote: > > All HDFS processes (NameNod

Re: Datanode can't connect namenode with kerberos

All HDFS processes (NameNodes, DataNodes, JournalNodes, FailoverControllers) to run as the same user, e.g. “hdfs”. > On 2018. Nov 9., at 8:35, Harinder Singh > wrote: > > I think you need a superuser to start the service. Is datanode a superuser? > > Regards > Harinder > > On Thu, Nov 8, 201

Re: Datanode can't connect namenode with kerberos

I think you need a superuser to start the service. Is datanode a superuser? Regards Harinder On Thu, Nov 8, 2018 at 11:29 PM ZongtianHou wrote: > Hi, everyone > I set up kerberos for the hdfs cluster, but after I start name node, then > the datanode, In the namenode log file, it display the fol