Ubuntu Hadoop namenode格式：未找到KeyProvider

我正试图在Ubuntu上安装Hadoop。我遵循了这个教程：而且一切似乎都很好。 但是，当我运行命令时：

hadoop namenode -format

我得到以下信息：

14/12/26 18:18:21 INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT]
14/12/26 18:18:21 INFO namenode.NameNode: createNameNode [-format]
14/12/26 18:18:22 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Formatting using clusterid: CID-b144d870-a74f-4c1c-8918-5b2fcef6805c
14/12/26 18:18:23 INFO namenode.FSNamesystem: No KeyProvider found.

在找到No-KeyProvider之后，进程完全停滞，没有输出

你知道问题是什么或如何调查吗？ 先谢谢你

编辑：jstack结果

2014-12-27 17:14:53
Full thread dump OpenJDK Zero VM (24.65-b04 mixed mode):

"Attach Listener" daemon prio=10 tid=0x70104060 nid=0xe88 waiting on condition [0x00000000]


 java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
    - None

"Service Thread" daemon prio=10 tid=0xb577e3c0 nid=0xd98 runnable [0x00000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
    - None

"Signal Dispatcher" daemon prio=10 tid=0xb577c9b8 nid=0xd97 runnable [0x00000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
    - None

"Finalizer" daemon prio=10 tid=0xb5769fd8 nid=0xd96 in Object.wait() [0x7045e000]
   java.lang.Thread.State: WAITING (on object monitor)
    at java.lang.Object.wait(Native Method)
    - waiting on <0x859e6a70> (a java.lang.ref.ReferenceQueue$Lock)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
    - locked <0x859e6a70> (a java.lang.ref.ReferenceQueue$Lock)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
    at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)

   Locked ownable synchronizers:
    - None

"Reference Handler" daemon prio=10 tid=0xb5768a80 nid=0xd95 in Object.wait() [0x705fe000]
   java.lang.Thread.State: WAITING (on object monitor)
    at java.lang.Object.wait(Native Method)
    - waiting on <0x859e6b00> (a java.lang.ref.Reference$Lock)
    at java.lang.Object.wait(Object.java:503)
    at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
    - locked <0x859e6b00> (a java.lang.ref.Reference$Lock)

   Locked ownable synchronizers:
    - None

"main" prio=10 tid=0xb570c4b0 nid=0xd93 runnable [0xb59a5000]
   java.lang.Thread.State: RUNNABLE
    at com.google.common.base.CharMatcher$12.setBits(CharMatcher.java:507)
    at com.google.common.base.CharMatcher$Or.setBits(CharMatcher.java:642)
    at com.google.common.base.CharMatcher.precomputedInternal(CharMatcher.java:673)
    at com.google.common.base.Platform.precomputeCharMatcher(Platform.java:53)
    at com.google.common.base.CharMatcher.precomputed(CharMatcher.java:657)
    at com.google.common.base.CharMatcher.<clinit>(CharMatcher.java:179)
    at com.google.common.base.Splitter.on(Splitter.java:125)
    at org.apache.hadoop.crypto.CryptoCodec.getCodecClasses(CryptoCodec.java:114)
    at org.apache.hadoop.crypto.CryptoCodec.getInstance(CryptoCodec.java:59)
    at org.apache.hadoop.crypto.CryptoCodec.getInstance(CryptoCodec.java:100)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:779)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:755)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:934)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1379)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1504)

   Locked ownable synchronizers:
    - None

"VM Thread" prio=10 tid=0xb5766130 nid=0xd94 runnable

"VM Periodic Task Thread" prio=10 tid=0xb5780058 nid=0xd99 waiting on condition

JNI global references: 355

---

KeyProvider消息应该是无害的。最近，hadoop添加了rest加密作为一项新功能。日志只是表示没有为此功能配置KeyProvider，但如果不使用该功能，则不需要此日志。您可以发布namenode进程的jstack来查看它在哪里卡住了吗？另外，namenode数据目录的权限设置是否正确，以便namenode写入？谢谢您的回答；我在帖子中添加了jstack结果。数据目录的权限设置为创建和删除Hadoop所有者的文件，并访问Hadoop组的文件。我猜这与CharMatchersetBits挂起的位置有关。询问者升级了番石榴以克服障碍。也许这对你有用？你的工作一直很有帮助。它现在起作用了。如果你编辑你的评论作为回答，我会引用它。非常感谢。