急!请教 hdfs格式化报错 bin/hdfs namenode -format

1. 执行日志如下:

17/12/23 08:34:18 INFO util.GSet: 0.029999999329447746% max memory 889 MB = 273.1 KB
17/12/23 08:34:18 INFO util.GSet: capacity      = 2^15 = 32768 entries
17/12/23 08:34:19 INFO namenode.NNConf: ACLs enabled? false
17/12/23 08:34:19 INFO namenode.NNConf: XAttrs enabled? true
17/12/23 08:34:19 INFO namenode.NNConf: Maximum size of an xattr: 16384
17/12/23 08:34:37 INFO client.QuorumJournalManager: Waited 18001 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:38 INFO client.QuorumJournalManager: Waited 19002 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:39 INFO client.QuorumJournalManager: Waited 20003 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:39 INFO ipc.Client: Retrying connect to server: ap3/59.110.217.95:8485. Already tried 0 time(s); maxRetries=45
17/12/23 08:34:39 INFO ipc.Client: Retrying connect to server: ap2/47.95.4.123:8485. Already tried 0 time(s); maxRetries=45
17/12/23 08:34:39 INFO ipc.Client: Retrying connect to server: ap1/39.106.177.169:8485. Already tried 0 time(s); maxRetries=45
17/12/23 08:34:40 INFO client.QuorumJournalManager: Waited 21004 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:41 INFO client.QuorumJournalManager: Waited 22005 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:42 INFO client.QuorumJournalManager: Waited 23006 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:43 INFO client.QuorumJournalManager: Waited 24007 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:44 INFO client.QuorumJournalManager: Waited 25008 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:45 INFO client.QuorumJournalManager: Waited 26009 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:46 INFO client.QuorumJournalManager: Waited 27010 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:47 INFO client.QuorumJournalManager: Waited 28011 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:48 INFO client.QuorumJournalManager: Waited 29012 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:49 INFO client.QuorumJournalManager: Waited 30013 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:50 INFO client.QuorumJournalManager: Waited 31014 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:51 INFO client.QuorumJournalManager: Waited 32015 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:52 INFO client.QuorumJournalManager: Waited 33016 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:53 INFO client.QuorumJournalManager: Waited 34017 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:54 INFO client.QuorumJournalManager: Waited 35018 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:55 INFO client.QuorumJournalManager: Waited 36019 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:56 INFO client.QuorumJournalManager: Waited 37020 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:57 INFO client.QuorumJournalManager: Waited 38021 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:58 INFO client.QuorumJournalManager: Waited 39022 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:59 INFO client.QuorumJournalManager: Waited 40023 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:34:59 INFO ipc.Client: Retrying connect to server: ap3/59.110.217.95:8485. Already tried 1 time(s); maxRetries=45
17/12/23 08:34:59 INFO ipc.Client: Retrying connect to server: ap2/47.95.4.123:8485. Already tried 1 time(s); maxRetries=45
17/12/23 08:34:59 INFO ipc.Client: Retrying connect to server: ap1/39.106.177.169:8485. Already tried 1 time(s); maxRetries=45
17/12/23 08:35:00 INFO client.QuorumJournalManager: Waited 41024 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:01 WARN client.QuorumJournalManager: Waited 42025 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:02 WARN client.QuorumJournalManager: Waited 43026 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:03 WARN client.QuorumJournalManager: Waited 44027 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:04 WARN client.QuorumJournalManager: Waited 45028 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:05 WARN client.QuorumJournalManager: Waited 46029 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:06 WARN client.QuorumJournalManager: Waited 47030 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:07 WARN client.QuorumJournalManager: Waited 48031 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:08 WARN client.QuorumJournalManager: Waited 49032 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:09 WARN client.QuorumJournalManager: Waited 50034 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:10 WARN client.QuorumJournalManager: Waited 51035 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:11 WARN client.QuorumJournalManager: Waited 52036 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:12 WARN client.QuorumJournalManager: Waited 53037 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:13 WARN client.QuorumJournalManager: Waited 54038 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:14 WARN client.QuorumJournalManager: Waited 55039 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:15 WARN client.QuorumJournalManager: Waited 56041 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:16 WARN client.QuorumJournalManager: Waited 57042 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:17 WARN client.QuorumJournalManager: Waited 58043 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:18 WARN client.QuorumJournalManager: Waited 59044 ms (timeout=60000 ms) for a response for hasSomeData. No responses yet.
17/12/23 08:35:19 WARN namenode.NameNode: Encountered exception during format: 
java.io.IOException: Timed out waiting for response from loggers
    at org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.hasSomeData(QuorumJournalManager.java:228)
    at org.apache.hadoop.hdfs.server.common.Storage.confirmFormat(Storage.java:899)
    at org.apache.hadoop.hdfs.server.namenode.FSImage.confirmFormat(FSImage.java:171)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:941)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1387)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1512)
17/12/23 08:35:19 INFO ipc.Client: Retrying connect to server: ap2/47.95.4.123:8485. Already tried 2 time(s); maxRetries=45
17/12/23 08:35:19 INFO ipc.Client: Retrying connect to server: ap3/59.110.217.95:8485. Already tried 2 time(s); maxRetries=45
17/12/23 08:35:19 INFO ipc.Client: Retrying connect to server: ap1/39.106.177.169:8485. Already 
 

要回复问题请先登录注册