1. Hadoop框架及使用

1. hadoop简介

hadoop起源于nutch，是根据谷歌的–分布式文件系统GFS–分布式计算框架Mapreduce开发。至今经历了0.x、1.x、2.x、3.x。

• 三大发行版
  • apache
  • hortonworks
  • clouderamanager

2. hadoop架构介绍

2.1 1.x架构模型

• 文件系统
  • namenode: 接受客户端的请求，管理集群中的元数据
  • secondarynamenode: 辅助namenode管理元数据信息
  • datanode: 主要职责是存储数据
• 计算系统
  • jobtracker: 接收客户端提交的计算任务，并且分配任务
  • tasktracker: 执行任务

2.2 2.x架构模型

1）单节点架构模型

• 文件系统模块
  • namenode: 接受客户端的请求，管理集群中的元数据
  • secondaryNameNode：辅助namenode管理元数据信息
  • DataNode：主要职责是存储数据
• 资源调度系统
  • ResourceManager：接收用户的计算请求任务，并负责集群的资源分配
  • NodeManager：负责执行主节点APPmaster分配的任务

2）namenode高可用

• 文件系统
  • namenode: 接受客户端的请求，管理集群中的元数据
  • datanode: 主要用于存储集群当中的各种数据
  • journalnode: 文件系统元数据信息管理
• 资源调度系统
  • ResourceManager：接收用户的计算请求任务，并负责集群的资源分配
  • NodeManager：负责执行主节点APPmaster分配的任务

3）resourcemanager高可用

• 文件系统模块
  • namenode: 接受客户端的请求，管理集群中的元数据
  • secondary : 辅助namenode管理元数据信息
  • datanode : 主要职责是存储数据
• 资源调度系统
  • ResourceManager：接收用户的计算请求任务，并负责集群的资源分配
  • NodeManager：负责执行主节点APPmaster分配的任务

4）namenode与resourcemanager都为高可用

• 文件系统
  • namenode: 接受客户端的请求，管理集群中的元数据
  • datanode: 主要用于存储集群当中的各种数据
  • journalnode: 文件系统元数据信息管理
• 资源调度系统
  • ResourceManager：接收用户的计算请求任务，并负责集群的资源分配
  • NodeManager：负责执行主节点APPmaster分配的任务

3. hadoop环境的搭建

3.1 standAlone

1）上传解压

2）修改配置文件

• core-site.xml

	<property>
		<name>fs.default.name</name>
		<value>hdfs://192.168.75.103:8020</value>
	</property>
	<property>
		<name>hadoop.tmp.dir</name>
		<value>/export/servers/hadoop-2.7.5/hadoopDatas/tempDatas</value>
	</property>
	<!--  缓冲区大小，实际工作中根据服务器性能动态调整 -->
	<property>
		<name>io.file.buffer.size</name>
		<value>4096</value>
	</property>

	<!--  开启hdfs的垃圾桶机制，删除掉的数据可以从垃圾桶中回收，单位分钟 -->
	<property>
		<name>fs.trash.interval</name>
		<value>10080</value>
	</property>

• hdfs-site.xml

<!-- NameNode存储元数据信息的路径，实际工作中，一般先确定磁盘的挂载目录，然后多个目录用，进行分割   --> 
	<!--   集群动态上下线 
	<property>
		<name>dfs.hosts</name>
		<value>/export/servers/hadoop-2.7.4/etc/hadoop/accept_host</value>
	</property>
	
	<property>
		<name>dfs.hosts.exclude</name>
		<value>/export/servers/hadoop-2.7.4/etc/hadoop/deny_host</value>
	</property>
	 -->
	 
	 <property>
			<name>dfs.namenode.secondary.http-address</name>
			<value>node01:50090</value>
	</property>

	<property>
		<name>dfs.namenode.http-address</name>
		<value>node01:50070</value>
	</property>
	<property>
		<name>dfs.namenode.name.dir</name>
		<value>file:///export/servers/hadoop-2.7.5/hadoopDatas/namenodeDatas,file:///export/servers/hadoop-2.7.5/hadoopDatas/namenodeDatas2</value>
	</property>
	<!--  定义dataNode数据存储的节点位置，实际工作中，一般先确定磁盘的挂载目录，然后多个目录用，进行分割  -->
	<property>
		<name>dfs.datanode.data.dir</name>
		<value>file:///export/servers/hadoop-2.7.5/hadoopDatas/datanodeDatas,file:///export/servers/hadoop-2.7.5/hadoopDatas/datanodeDatas2</value>
	</property>
	
	<property>
		<name>dfs.namenode.edits.dir</name>
		<value>file:///export/servers/hadoop-2.7.5/hadoopDatas/nn/edits</value>
	</property>
	

	<property>
		<name>dfs.namenode.checkpoint.dir</name>
		<value>file:///export/servers/hadoop-2.7.5/hadoopDatas/snn/name</value>
	</property>
	<property>
		<name>dfs.namenode.checkpoint.edits.dir</name>
		<value>file:///export/servers/hadoop-2.7.5/hadoopDatas/dfs/snn/edits</value>
	</property>

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

	<property>
		<name>dfs.permissions</name>
		<value>false</value>
	</property>

	<property>
		<name>dfs.blocksize</name>
		<value>134217728</value>
	</property>

• hadoop-env.sh

export JAVA_HOME=/export/servers/jdk1.8.0_141

• map-site.xml

	<property>
		<name>mapreduce.framework.name</name>
		<value>yarn</value>
	</property>

	<property>
		<name>mapreduce.job.ubertask.enable</name>
		<value>true</value>
	</property>
	
	<property>
		<name>mapreduce.jobhistory.address</name>
		<value>node01:10020</value>
	</property>

	<property>
		<name>mapreduce.jobhistory.webapp.address</name>
		<value>node01:19888</value>
	</property>

• yarn-site.xml

	<property>
		<name>yarn.resourcemanager.hostname</name>
		<value>node01</value>
	</property>
	<property>
		<name>yarn.nodemanager.aux-services</name>
		<value>mapreduce_shuffle</value>
	</property>
	
	<property>
		<name>yarn.log-aggregation-enable</name>
		<value>true</value>
	</property>
	<property>
		<name>yarn.log-aggregation.retain-seconds</name>
		<value>604800</value>
	</property>

• slaves

localhost

3）启动集群

首次启动 HDFS 时，必须对其进行格式化操作。 本质上是一些清理和

准备工作，因为此时的 HDFS 在物理上还是不存在的。

hdfs namenode -format

创建数据存放文件夹

cd  /export/servers/hadoop-2.7.5
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/tempDatas
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/namenodeDatas
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/namenodeDatas2
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/datanodeDatas
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/datanodeDatas2
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/nn/edits
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/snn/name
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/dfs/snn/edits

启动服务

cd  /export/servers/hadoop-2.7.5/
bin/hdfs namenode -format
sbin/start-dfs.sh
sbin/start-yarn.sh
sbin/mr-jobhistory-daemon.sh start historyserver

UI界面查看

http://node01:50070/explorer.html#/ 查看hdfs

http://node01:8088/cluster 查看yarn集群

http://node01:19888/jobhistory 查看历史完成的任务

3.2 伪分布式

在单机的基础之上

1）删除hadoopDatas然后重新创建文件夹

rm  -rf  /export/servers/hadoop-2.7.5/hadoopDatas

2）重新创建数据文件

mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/tempDatas
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/namenodeDatas
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/namenodeDatas2
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/datanodeDatas
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/datanodeDatas2
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/nn/edits
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/snn/name
mkdir -p /export/servers/hadoop-2.7.5/hadoopDatas/dfs/snn/edits

3）修改slaves文件为

node01
node02
node03

5）安装包分发到其他机器

cd  /export/servers/
scp -r hadoop-2.7.5 node02:$PWD
scp -r hadoop-2.7.5 node03:$PWD

6）启动集群

cd  /export/servers/hadoop-2.7.5
bin/hdfs namenode -format
sbin/start-dfs.sh
sbin/start-yarn.sh
sbin/mr-jobhistory-daemon.sh start historyserver

3.3 完全分布式

1）上传解压

2）配置文件

• core-site.xml

	<!-- 指定NameNode的HA高可用的zk地址  -->
	<property>
		<name>ha.zookeeper.quorum</name>
		<value>node01:2181,node02:2181,node03:2181</value>
	</property>
	 <!-- 指定HDFS访问的域名地址  -->
	<property>
		<name>fs.defaultFS</name>
		<value>hdfs://ns</value>
	</property>
	 <!-- 临时文件存储目录  -->
	<property>
		<name>hadoop.tmp.dir</name>
		<value>/export/servers/hadoop-2.7.5/data/tmp</value>
	</property>
	 <!-- 开启hdfs垃圾箱机制，指定垃圾箱中的文件七天之后就彻底删掉
			单位为分钟
	 -->
	<property>
		<name>fs.trash.interval</name>
		<value>10080</value>
	</property>

• hdfs-site.xml

	<!--  指定命名空间  -->
	<property>
		<name>dfs.nameservices</name>
		<value>ns</value>
	</property>
	<!--  指定该命名空间下的两个机器作为我们的NameNode  -->
	<property>
		<name>dfs.ha.namenodes.ns</name>
		<value>nn1,nn2</value>
	</property>

	<!-- 配置第一台服务器的namenode通信地址  -->
	<property>
		<name>dfs.namenode.rpc-address.ns.nn1</name>
		<value>node01:8020</value>
	</property>
	<!--  配置第二台服务器的namenode通信地址  -->
	<property>
		<name>dfs.namenode.rpc-address.ns.nn2</name>
		<value>node02:8020</value>
	</property>
	<!-- 所有从节点之间相互通信端口地址 -->
	<property>
		<name>dfs.namenode.servicerpc-address.ns.nn1</name>
		<value>node01:8022</value>
	</property>
	<!-- 所有从节点之间相互通信端口地址 -->
	<property>
		<name>dfs.namenode.servicerpc-address.ns.nn2</name>
		<value>node02:8022</value>
	</property>
	
	<!-- 第一台服务器namenode的web访问地址  -->
	<property>
		<name>dfs.namenode.http-address.ns.nn1</name>
		<value>node01:50070</value>
	</property>
	<!-- 第二台服务器namenode的web访问地址  -->
	<property>
		<name>dfs.namenode.http-address.ns.nn2</name>
		<value>node02:50070</value>
	</property>
	
	<!-- journalNode的访问地址，注意这个地址一定要配置 -->
	<property>
		<name>dfs.namenode.shared.edits.dir</name>
		<value>qjournal://node01:8485;node02:8485;node03:8485/ns1</value>
	</property>
	<!--  指定故障自动恢复使用的哪个java类 -->
	<property>
		<name>dfs.client.failover.proxy.provider.ns</name>
		<value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider</value>
	</property>
	
	<!-- 故障转移使用的哪种通信机制 -->
	<property>
		<name>dfs.ha.fencing.methods</name>
		<value>sshfence</value>
	</property>
	
	<!-- 指定通信使用的公钥  -->
	<property>
		<name>dfs.ha.fencing.ssh.private-key-files</name>
		<value>/root/.ssh/id_rsa</value>
	</property>
	<!-- journalNode数据存放地址  -->
	<property>
		<name>dfs.journalnode.edits.dir</name>
		<value>/export/servers/hadoop-2.7.5/data/dfs/jn</value>
	</property>
	<!-- 启用自动故障恢复功能 -->
	<property>
		<name>dfs.ha.automatic-failover.enabled</name>
		<value>true</value>
	</property>
	<!-- namenode产生的文件存放路径 -->
	<property>
		<name>dfs.namenode.name.dir</name>
		<value>file:///export/servers/hadoop-2.7.5/data/dfs/nn/name</value>
	</property>
	<!-- edits产生的文件存放路径 -->
	<property>
		<name>dfs.namenode.edits.dir</name>
		<value>file:///export/servers/hadoop-2.7.5/data/dfs/nn/edits</value>
	</property>
	<!-- dataNode文件存放路径 -->
	<property>
		<name>dfs.datanode.data.dir</name>
		<value>file:///export/servers/hadoop-2.7.5/data/dfs/dn</value>
	</property>
	<!-- 关闭hdfs的文件权限 -->
	<property>
		<name>dfs.permissions</name>
		<value>false</value>
	</property>
	<!-- 指定block文件块的大小 -->
	<property>
		<name>dfs.blocksize</name>
		<value>134217728</value>
	</property>

• yarn-site.xml（node03与node02稍有不同）

<configuration>
<!-- Site specific YARN configuration properties -->
<!-- 是否启用日志聚合.应用程序完成后,日志汇总收集每个容器的日志,这些日志移动到文件系统,例如HDFS. -->
<!-- 用户可以通过配置"yarn.nodemanager.remote-app-log-dir"、"yarn.nodemanager.remote-app-log-dir-suffix"来确定日志移动到的位置 -->
<!-- 用户可以通过应用程序时间服务器访问日志 -->

<!-- 启用日志聚合功能，应用程序完成后，收集各个节点的日志到一起便于查看 -->
<property>
		<name>yarn.log-aggregation-enable</name>
		<value>true</value>
</property>
 

<!--开启resource manager HA,默认为false--> 
<property>
        <name>yarn.resourcemanager.ha.enabled</name>
        <value>true</value>
</property>
<!-- 集群的Id，使用该值确保RM不会做为其它集群的active -->
<property>
        <name>yarn.resourcemanager.cluster-id</name>
        <value>mycluster</value>
</property>
<!--配置resource manager  命名-->
<property>
        <name>yarn.resourcemanager.ha.rm-ids</name>
        <value>rm1,rm2</value>
</property>
<!-- 配置第一台机器的resourceManager -->
<property>
        <name>yarn.resourcemanager.hostname.rm1</name>
        <value>node03</value>
</property>
<!-- 配置第二台机器的resourceManager -->
<property>
        <name>yarn.resourcemanager.hostname.rm2</name>
        <value>node02</value>
</property>

<!-- 配置第一台机器的resourceManager通信地址 -->
<property>
        <name>yarn.resourcemanager.address.rm1</name>
        <value>node03:8032</value>
</property>
<property>
        <name>yarn.resourcemanager.scheduler.address.rm1</name>
        <value>node03:8030</value>
</property>
<property>
        <name>yarn.resourcemanager.resource-tracker.address.rm1</name>
        <value>node03:8031</value>
</property>
<property>
        <name>yarn.resourcemanager.admin.address.rm1</name>
        <value>node03:8033</value>
</property>
<property>
        <name>yarn.resourcemanager.webapp.address.rm1</name>
        <value>node03:8088</value>
</property>

<!-- 配置第二台机器的resourceManager通信地址 -->
<property>
        <name>yarn.resourcemanager.address.rm2</name>
        <value>node02:8032</value>
</property>
<property>
        <name>yarn.resourcemanager.scheduler.address.rm2</name>
        <value>node02:8030</value>
</property>
<property>
        <name>yarn.resourcemanager.resource-tracker.address.rm2</name>
        <value>node02:8031</value>
</property>
<property>
        <name>yarn.resourcemanager.admin.address.rm2</name>
        <value>node02:8033</value>
</property>
<property>
        <name>yarn.resourcemanager.webapp.address.rm2</name>
        <value>node02:8088</value>
</property>
<!--开启resourcemanager自动恢复功能-->
<property>
        <name>yarn.resourcemanager.recovery.enabled</name>
        <value>true</value>
</property>
<!--在node1上配置rm1,在node2上配置rm2,注意：一般都喜欢把配置好的文件远程复制到其它机器上，但这个在YARN的另一个机器上一定要修改，其他机器上不配置此项-->
	<property>
		<name>yarn.resourcemanager.ha.id</name>
		<value>rm1</value> 
       <description>If we want to launch more than one RM in single node, we need this configuration</description>
	</property>
	   
	   <!--用于持久存储的类。尝试开启-->
<property>
        <name>yarn.resourcemanager.store.class</name>
        <value>org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore</value>
</property>
<property>
        <name>yarn.resourcemanager.zk-address</name>
        <value>node02:2181,node03:2181,node01:2181</value>
        <description>For multiple zk services, separate them with comma</description>
</property>
<!--开启resourcemanager故障自动切换，指定机器--> 
<property>
        <name>yarn.resourcemanager.ha.automatic-failover.enabled</name>
        <value>true</value>
        <description>Enable automatic failover; By default, it is enabled only when HA is enabled.</description>
</property>
<property>
        <name>yarn.client.failover-proxy-provider</name>
        <value>org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider</value>
</property>
<!-- 允许分配给一个任务最大的CPU核数，默认是8 -->
<property>
        <name>yarn.nodemanager.resource.cpu-vcores</name>
        <value>4</value>
</property>
<!-- 每个节点可用内存,单位MB -->
<property>
        <name>yarn.nodemanager.resource.memory-mb</name>
        <value>512</value>
</property>
<!-- 单个任务可申请最少内存，默认1024MB -->
<property>
        <name>yarn.scheduler.minimum-allocation-mb</name>
        <value>512</value>
</property>
<!-- 单个任务可申请最大内存，默认8192MB -->
<property>
        <name>yarn.scheduler.maximum-allocation-mb</name>
        <value>512</value>
</property>
<!--多长时间聚合删除一次日志 此处-->
<property>
        <name>yarn.log-aggregation.retain-seconds</name>
        <value>2592000</value><!--30 day-->
</property>
<!--时间在几秒钟内保留用户日志。只适用于如果日志聚合是禁用的-->
<property>
        <name>yarn.nodemanager.log.retain-seconds</name>
        <value>604800</value><!--7 day-->
</property>
<!--指定文件压缩类型用于压缩汇总日志-->
<property>
        <name>yarn.nodemanager.log-aggregation.compression-type</name>
        <value>gz</value>
</property>
<!-- nodemanager本地文件存储目录-->
<property>
        <name>yarn.nodemanager.local-dirs</name>
        <value>/export/servers/hadoop-2.7.5/yarn/local</value>
</property>
<!-- resourceManager  保存最大的任务完成个数 -->
<property>
        <name>yarn.resourcemanager.max-completed-applications</name>
        <value>1000</value>
</property>
<!-- 逗号隔开的服务列表，列表名称应该只包含a-zA-Z0-9_,不能以数字开始-->
<property>
        <name>yarn.nodemanager.aux-services</name>
        <value>mapreduce_shuffle</value>
</property>

<!--rm失联后重新链接的时间--> 
<property>
        <name>yarn.resourcemanager.connect.retry-interval.ms</name>
        <value>2000</value>
</property>
</configuration>

• 修改mapred-site.xml

<!-- 指定运行mapreduce的环境是yarn -->
<property>
        <name>mapreduce.framework.name</name>
        <value>yarn</value>
</property>
<!-- MapReduce JobHistory Server IPC host:port -->
<property>
        <name>mapreduce.jobhistory.address</name>
        <value>node03:10020</value>
</property>
<!-- MapReduce JobHistory Server Web UI host:port -->
<property>
        <name>mapreduce.jobhistory.webapp.address</name>
        <value>node03:19888</value>
</property>
<!-- The directory where MapReduce stores control files.默认 ${hadoop.tmp.dir}/mapred/system -->
<property>
        <name>mapreduce.jobtracker.system.dir</name>
        <value>/export/servers/hadoop-2.7.5/data/system/jobtracker</value>
</property>
<!-- The amount of memory to request from the scheduler for each map task. 默认 1024-->
<property>
        <name>mapreduce.map.memory.mb</name>
        <value>1024</value>
</property>
<!-- <property>
                <name>mapreduce.map.java.opts</name>
                <value>-Xmx1024m</value>
        </property> -->
<!-- The amount of memory to request from the scheduler for each reduce task. 默认 1024-->
<property>
        <name>mapreduce.reduce.memory.mb</name>
        <value>1024</value>
</property>
<!-- <property>
               <name>mapreduce.reduce.java.opts</name>
               <value>-Xmx2048m</value>
        </property> -->
<!-- 用于存储文件的缓存内存的总数量，以兆字节为单位。默认情况下，分配给每个合并流1MB，给个合并流应该寻求最小化。默认值100-->
<property>
        <name>mapreduce.task.io.sort.mb</name>
        <value>100</value>
</property>
 
<!-- <property>
        <name>mapreduce.jobtracker.handler.count</name>
        <value>25</value>
        </property>-->
<!-- 整理文件时用于合并的流的数量。这决定了打开的文件句柄的数量。默认值10-->
<property>
        <name>mapreduce.task.io.sort.factor</name>
        <value>10</value>
</property>
<!-- 默认的并行传输量由reduce在copy(shuffle)阶段。默认值5-->
<property>
        <name>mapreduce.reduce.shuffle.parallelcopies</name>
        <value>25</value>
</property>
<property>
        <name>yarn.app.mapreduce.am.command-opts</name>
        <value>-Xmx1024m</value>
</property>
<!-- MR AppMaster所需的内存总量。默认值1536-->
<property>
        <name>yarn.app.mapreduce.am.resource.mb</name>
        <value>1536</value>
</property>
<!-- MapReduce存储中间数据文件的本地目录。目录不存在则被忽略。默认值${hadoop.tmp.dir}/mapred/local-->
<property>
        <name>mapreduce.cluster.local.dir</name>
        <value>/export/servers/hadoop-2.7.5/data/system/local</value>
</property>

• slaves

node01
node02
node03

• hadoop-env.sh

export JAVA_HOME=/export/servers/jdk1.8.0_141

3）启动集群

• 分发到其他机器

cd /export/servers
scp -r hadoop-2.7.5/ node02:$PWD
scp -r hadoop-2.7.5/ node03:$PWD

• 所有的机器上创建所需目录

mkdir -p /export/servers/hadoop-2.7.5/data/dfs/nn/name
mkdir -p /export/servers/hadoop-2.7.5/data/dfs/nn/edits
mkdir -p /export/servers/hadoop-2.7.5/data/dfs/nn/name
mkdir -p /export/servers/hadoop-2.7.5/data/dfs/nn/edits

• 更改node02上的rm1为rm2

	<property>       
		<name>yarn.resourcemanager.ha.id</name>
		<value>rm2</value>
       <description>If we want to launch more than one RM in single node, we need this configuration</description>
	</property>

• 启动hdfs

  • node01上执行

  bin/hdfs zkfc -formatZK
  sbin/hadoop-daemons.sh start journalnode
  
  bin /hdfs namenode -format
  bin/hdfs namenode -initializeSharedEdits -force
  sbin/start-dfs.sh
  

  • node02执行

  bin/hdfs namenode -bootstrapStandby
  sbin/hadoop-daemon.sh start namenode
  

• 启动yarn

  • node03上执行

  sbin/start-yarn.sh
  

  • node02上执行

  sbin/start-yarn.sh
  

  • 查看两台机器上的resourcemanager的状态

  node03上
  bin/yarn rmadmin -getServiceState rm1
  
  node02上
  bin/yarn rmadmin -getServiceState rm2
  
  

• 启动jobHistory

node03上启动JobHistory
sbin/mr-jobhistory-daemon.sh start historyserver

UI界面查看

http://node01:50070/explorer.html#/ 查看hdfs

http://node03:8088/cluster 查看yarn集群

http://node03:19888/jobhistory 查看历史完成的任务

3.4 CDH版本的hadoop

CDH版本的Hadoop安装和apache的hadoop安装相同，主要是要会自己编译

1）编译环境准备

• 准备一台linux环境，内存4G或以上，硬盘40G或以上，我这里使用的是Centos6.9 64位的操作系统

• 虚拟机联网、关闭防火墙、关闭selinux

• 安装jdk1.7、配置环境变量

• 安装maven、配置环境变量

• 添加maven仓库

• 安装findbugs

  1）下载

cd  /export/softwares
wget --no-check-certificate https://sourceforge.net/projects/findbugs/files/findbugs/1.3.9/findbugs-1.3.9.tar.gz/download -O findbugs-1.3.9.tar.gz

​ 2）解压

tar -zxvf findbugs-1.3.9.tar.gz -C ../servers/

​ 3）配置环境变量

export FINDBUGS_HOME=/export/servers/findbugs-1.3.9
export PATH=:$FINDBUGS_HOME/bin:$PATH

​ 4）source /etc/profile

• 在线安装一些依赖包

yum install autoconf automake libtool cmake
yum install ncurses-devel
yum install openssl-devel
yum install lzo-devel zlib-devel gcc gcc-c++
yum install -y  bzip2-devel

• 安装protobuf

cd  /export/softwares
tar -zxvf protobuf-2.5.0.tar.gz -C ../servers/
cd   /export/servers/protobuf-2.5.0
./configure
make && make install

• 安装snappy

cd /export/softwares/
tar -zxf snappy-1.1.1.tar.gz  -C ../servers/
cd ../servers/snappy-1.1.1/
./configure
make && make install

2）下载源码准备编译

cd  /export/softwares
wget http://archive.cloudera.com/cdh5/cdh/5/hadoop-2.6.0-cdh5.14.0-src.tar.gz
tar -zxvf hadoop-2.6.0-cdh5.14.0-src.tar.gz -C ../servers/
cd  /export/servers/hadoop-2.6.0-cdh5.14.0

• 编译不支持snappy压缩

mvn package -Pdist,native -DskipTests –Dtar  

• 编译支持snappy压缩

mvn package -DskipTests -Pdist,native -Dtar -Drequire.snappy -e -X

• 常见编译错误

An Ant BuildException has occured: exec returned: 2

这是因为tomcat的压缩包没有下载完成，需要自己下载一个对应版本的apache-tomcat-6.0.53.tar.gz的压缩包放到指定路径下面去即可：

这两个路径下面需要放上这个tomcat的 压缩包

/export/servers/hadoop-2.6.0-cdh5.14.0/hadoop-hdfs-project/hadoop-hdfs-httpfs/downloads

/export/servers/hadoop-2.6.0-cdh5.14.0/hadoop-common-project/hadoop-kms/downloads

4. hadoop基本命令

4.1 hdfs的基本命令

• ls

  Usage: hdfs dfs -ls [-R] <args>
  Options:
  •	The -R option will return stat recursively through the directory structure.
  For a file returns stat on the file with the following format:
  permissions number_of_replicas userid groupid filesize modification_date modification_time filename
  For a directory it returns list of its direct children as in Unix. A directory is listed as:
  permissions userid groupid modification_date modification_time dirname
  Example:
  •	hdfs dfs -ls /user/hadoop/file1
  Exit Code:
  Returns 0 on success and -1 on error.
  

• lsr

  Usage: hdfs dfs -lsr <args>
  Recursive version of ls.
  Note: This command is deprecated. Instead use hdfs dfs -ls -R
  

• mkdir

  Usage: hdfs dfs -mkdir [-p] <paths>
  Takes path uri's as argument and creates directories.
  Options:
  •	The -p option behavior is much like Unix mkdir -p, creating parent directories along the path.
  Example:
  •	hdfs dfs -mkdir /user/hadoop/dir1 /user/hadoop/dir2
  •	hdfs dfs -mkdir hdfs://nn1.example.com/user/hadoop/dir hdfs://nn2.example.com/user/hadoop/dir
  Exit Code:
  Returns 0 on success and -1 on error.
  

• moveFromLocal

  Usage: hdfs dfs -moveFromLocal <localsrc> <dst>
  Similar to put command, except that the source localsrc is deleted after it's copied.
  

• moveToFile

  Usage: hdfs dfs -moveToLocal [-crc] <src> <dst>
  Displays a "Not implemented yet" message.
  

• mv

  Usage: hdfs dfs -mv URI [URI ...] <dest>
  Moves files from source to destination. This command allows multiple sources as well in which case the destination needs to be a directory. Moving files across file systems is not permitted.
  Example:
  •	hdfs dfs -mv /user/hadoop/file1 /user/hadoop/file2
  •	hdfs dfs -mv hdfs://nn.example.com/file1 hdfs://nn.example.com/file2 hdfs://nn.example.com/file3 hdfs://nn.example.com/dir1
  Exit Code:
  Returns 0 on success and -1 on error.
  

• put

  Usage: hdfs dfs -put <localsrc> ... <dst>
  Copy single src, or multiple srcs from local file system to the destination file system. Also reads input from stdin and writes to destination file system.
  •	hdfs dfs -put localfile /user/hadoop/hadoopfile
  •	hdfs dfs -put localfile1 localfile2 /user/hadoop/hadoopdir
  •	hdfs dfs -put localfile hdfs://nn.example.com/hadoop/hadoopfile
  •	hdfs dfs -put - hdfs://nn.example.com/hadoop/hadoopfile Reads the input from stdin.
  Exit Code:
  Returns 0 on success and -1 on error.
  

• appendToFile

  Usage: hdfs dfs -appendToFile <localsrc> ... <dst>
  追加一个或者多个文件到hdfs指定文件中.也可以从命令行读取输入.
  •	hdfs dfs -appendToFile localfile /user/hadoop/hadoopfile
  •	hdfs dfs -appendToFile localfile1 localfile2 /user/hadoop/hadoopfile
  •	hdfs dfs -appendToFile localfile hdfs://nn.example.com/hadoop/hadoopfile
  •	hdfs dfs -appendToFile - hdfs://nn.example.com/hadoop/hadoopfile Reads the input from stdin.
  Exit Code:
  Returns 0 on success and 1 on error.
  

• cat

  Usage: hdfs dfs -cat URI [URI ...]
  查看内容.
  Example:
  •	hdfs dfs -cat hdfs://nn1.example.com/file1 hdfs://nn2.example.com/file2
  •	hdfs dfs -cat file:///file3 /user/hadoop/file4
  Exit Code:
  Returns 0 on success and -1 on error.
  

• cp

  Usage: hdfs dfs -cp [-f] [-p | -p[topax]] URI [URI ...] <dest>
  复制文件(夹)，可以覆盖，可以保留原有权限信息
  Options:
  •	The -f option will overwrite the destination if it already exists.
  •	The -p option will preserve file attributes [topx] (timestamps, ownership, permission, ACL, XAttr). If -p is specified with no arg, then preserves timestamps, ownership, permission. If -pa is specified, then preserves permission also because ACL is a super-set of permission. Determination of whether raw namespace extended attributes are preserved is independent of the -p flag.
  Example:
  •	hdfs dfs -cp /user/hadoop/file1 /user/hadoop/file2
  •	hdfs dfs -cp /user/hadoop/file1 /user/hadoop/file2 /user/hadoop/dir
  Exit Code:
  Returns 0 on success and -1 on error.
  

• rm

  Usage: hdfs dfs -rm [-f] [-r|-R] [-skipTrash] URI [URI ...]
  Delete files specified as args.
  Options:
  •	The -f option will not display a diagnostic message or modify the exit status to reflect an error if the file does not exist.
  •	The -R option deletes the directory and any content under it recursively.
  •	The -r option is equivalent to -R.
  •	The -skipTrash option will bypass trash, if enabled, and delete the specified file(s) immediately. This can be useful when it is necessary to delete files from an over-quota directory.
  Example:
  •	hdfs dfs -rm hdfs://nn.example.com/file /user/hadoop/emptydir
  Exit Code:
  Returns 0 on success and -1 on error.
  

• rmr

  Usage: hdfs dfs -rmr [-skipTrash] URI [URI ...]
  Recursive version of delete.
  Note: This command is deprecated. Instead use hdfs dfs -rm -r
  

• chmod

  Usage: hdfs dfs -chmod [-R] <MODE[,MODE]... | OCTALMODE> URI [URI ...]
  修改权限.
  Options
  •	The -R option will make the change recursively through the directory structure.
  

• chown

  Usage: hdfs dfs -chown [-R] [OWNER][:[GROUP]] URI [URI ]
  修改所有者.
  Options
  •	The -R option will make the change recursively through the directory structure.
  

• expunge

  Usage: hdfs dfs -expunge
  清空回收站.
  

4.2 mapreduce的任务提交

1）写入测试

hadoop jar /export/servers/hadoop-2.6.0-cdh5.14.0/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.6.0-cdh5.14.0.jar TestDFSIO  -write -nrFiles 10 -fileSize 10MB

查看测试结果

hdfs dfs -text /benchmarks/TestDFSIO/io_write/part-00000

2）读取测试

hadoop jar /export/servers/hadoop-2.6.0-cdh5.14.0/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.6.0-cdh5.14.0.jar TestDFSIO -read -nrFiles 10 -fileSize 10MB

查看测试结果

hdfs dfs -text /benchmarks/TestDFSIO/io_read/part-00000

3）清除测试数据

hadoop jar /export/servers/hadoop-2.6.0-cdh5.14.0/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.6.0-cdh5.14.0.jar TestDFSIO -clean