Hadoop 名称节点永远不会离开安全模式，即使所有文件都未损坏并且jps显示名称节点两次

我使用（brew安装hadoop）安装了hadoop。4个月来，它一直正常运行。我意识到mapred-site.xml被配置为jobtracker So。我改为纱线并重新启动，然后发现数据节点丢失。我重新安装了hadoop，发现了一些损坏的文件。我用fsck删除了那个文件。但名称节点仍将保持在安全模式。我尝试了5次重新安装hadoop，也卸载了brew并再次安装了all fresh。我还没弄明白。任何帮助都将不胜感激。我这周有作业要完成

太平绅士

core-site.xml

 <property>
  <name>hadoop.tmp.dir</name>
  <value>/usr/local/Cellar/hadoop/hdfs/tmp</value>
</property>
<property>
    <name>fs.defaultFS</name>
    <value>hdfs://localhost:9000</value>
</property>

<property>
    <name>dfs.replication</name>
    <value>1</value>
</property>

   <property>
    <name>yarn.nodemanager.aux-services</name>
    <value>mapreduce_shuffle</value>
</property>

hdfs fsck/| egrep-v'^.+$'| grep-v eplica

    Connecting to namenode via            http://localhost:50070/fsckugi=krishnaprasad&path=%2F
    FSCK started by krishnaprasad (auth:SIMPLE) from /127.0.0.1 for    path / at Fri Jan 13 12:07:11 PST 2017
     Status: HEALTHY
     Total size:    0 B
     Total dirs:    1
     Total files:   0
     Total symlinks:        0
     Total blocks (validated):  0
     Corrupt blocks:        0
     Number of data-nodes:      1
     Number of racks:       1
     FSCK ended at Fri Jan 13 12:07:11 PST 2017 in 3 milliseconds
     The filesystem under path '/' is HEALTHY

---

dfsadmin-report

显示缺少26个块（看起来像整个hdfs），这就是namenode仍处于安全模式的原因。hdfs fsck-list corruptfileblocks显示0个损坏的文件您没有任何损坏的块，但缺少块。如果您没有实际的数据块，但元数据存在，则会出现这种情况。请告诉我如何解决此问题。非常感谢。为什么名称节点显示两次？我多次尝试格式化名称节点，但都不起作用：(

   <property>
    <name>yarn.nodemanager.aux-services</name>
    <value>mapreduce_shuffle</value>
</property>

    Safe mode is ON
    Configured Capacity: 120124866560 (111.88 GB)
    Present Capacity: 40319258624 (37.55 GB)
    DFS Remaining: 40319250432 (37.55 GB)
    DFS Used: 8192 (8 KB)
    DFS Used%: 0.00%
    Under replicated blocks: 0
    Blocks with corrupt replicas: 0
    Missing blocks: 0
    Missing blocks (with replication factor 1): 26
    -------------------------------------------------
    Live datanodes (1):

    Name: 127.0.0.1:50010 (localhost)
    Hostname: 192.168.0.15
    Decommission Status : Normal
    Configured Capacity: 120124866560 (111.88 GB)
    DFS Used: 8192 (8 KB)
    Non DFS Used: 79805607936 (74.32 GB)
    DFS Remaining: 40319250432 (37.55 GB)
    DFS Used%: 0.00%
    DFS Remaining%: 33.56%
    Configured Cache Capacity: 0 (0 B)
    Cache Used: 0 (0 B)
    Cache Remaining: 0 (0 B)
    Cache Used%: 100.00%
    Cache Remaining%: 0.00%
    Xceivers: 1
    Last contact: Fri Jan 13 11:41:49 PST 2017

    Connecting to namenode via            http://localhost:50070/fsckugi=krishnaprasad&path=%2F
    FSCK started by krishnaprasad (auth:SIMPLE) from /127.0.0.1 for    path / at Fri Jan 13 12:07:11 PST 2017
     Status: HEALTHY
     Total size:    0 B
     Total dirs:    1
     Total files:   0
     Total symlinks:        0
     Total blocks (validated):  0
     Corrupt blocks:        0
     Number of data-nodes:      1
     Number of racks:       1
     FSCK ended at Fri Jan 13 12:07:11 PST 2017 in 3 milliseconds
     The filesystem under path '/' is HEALTHY