Namenode启动时，每个端口都去认证一次，且认证失败

Question

HDNamenode在启动时，发现每个端口都去认证了一次，使用的用户名为null，而且认证失败了。
但是整个HDFS的功能又是正常的，这是什么原因啊。
2019-01-11 00:27:08,407 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:49972:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:10,612 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:49984:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:11,651 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:49987:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:11,653 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:49988:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:15,495 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:50006:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:16,230 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:50058:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:17,101 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:50094:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:21,266 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:50118:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:25,949 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:50135:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:25,952 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:50136:null (GSS initiate failed) with true cause: (GSS initiate failed)
2019-01-11 00:27:27,639 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 172.28.128.61:50216:null (GSS initiate failed) with true cause: (GSS initiate failed)

Answer 1

去检查一下你的延时设置吧