hadoop 集群启动时 Address already in use 解决方法

搭建好hadoop集群之后，运行start-all.sh脚本，发现有如下报错

starting namenode, logging to /usr/local/hadoop/libexec/../logs/hadoop-hadoop-namenode-we-home-server.out
homeserver: starting datanode, logging to /usr/local/hadoop/libexec/../logs/hadoop-hadoop-datanode-homeserver.out
we-home-server: starting secondarynamenode, logging to /usr/local/hadoop/libexec/../logs/hadoop-hadoop-secondarynamenode-we-home-server.out
we-home-server: Exception in thread "main" java.net.BindException: Address already in use
we-home-server:         at sun.nio.ch.Net.bind(Native Method)
we-home-server:         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124)
we-home-server:         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
we-home-server:         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
we-home-server:         at org.apache.hadoop.http.HttpServer.start(HttpServer.java:581)
we-home-server:         at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$1.run(SecondaryNameNode.java:216)
we-home-server:         at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$1.run(SecondaryNameNode.java:190)
we-home-server:         at java.security.AccessController.doPrivileged(Native Method)
we-home-server:         at javax.security.auth.Subject.doAs(Subject.java:396)
starting jobtracker, logging to /usr/local/hadoop/libexec/../logs/hadoop-hadoop-jobtracker-we-home-server.out

log中说明错误 Address already in use，这是因为有上次的运行datanode的进程没有终止，解决方法，

netstat -antup

运行这个命令后，找出占用50030端口的那个进程的PID，然后将其终止

kill -9 <PID>

然后，再重新启动hadoop集群，没有报错。

hadoop@we-home-server:/usr/local/hadoop/bin$ ./start-all.sh
starting namenode, logging to /usr/local/hadoop/libexec/../logs/hadoop-hadoop-namenode-we-home-server.out
homeserver: starting datanode, logging to /usr/local/hadoop/libexec/../logs/hadoop-hadoop-datanode-homeserver.out
we-home-server: starting secondarynamenode, logging to /usr/local/hadoop/libexec/../logs/hadoop-hadoop-secondarynamenode-we-home-server.out
starting jobtracker, logging to /usr/local/hadoop/libexec/../logs/hadoop-hadoop-jobtracker-we-home-server.out
homeserver: starting tasktracker, logging to /usr/local/hadoop/libexec/../logs/hadoop-hadoop-tasktracker-homeserver.out
hadoop@we-home-server:/usr/local/hadoop/bin$

转载于:https://www.cnblogs.com/lxs0731/archive/2013/03/17/2964913.html

hadoop 集群启动时 Address already in use 解决方法相关推荐

Hadoop集群启动时NameNode未启动解决方法
最近,我在学习搭建hadoop集群,可是搭建完成后当使用start-all.sh启动hadoop集群的时候,发现NameNode未启动,我经过反复查询发现是因为datanode的clusterID不匹 ...
Hadoop集群启动时,nameNode进程没有启动 :Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password)解决方法
前言今天搭建Hadoop集群的最后,启动hadoop集群后,发现nameNode进程并没有启动,基于相信自己的原则,我一直认为我已经将生成的公钥添加到本地的认证文件中,排查了半天,最终还是选择,查看 ...
Hadoop集群启动、初体验
1．启动方式要启动Hadoop集群,需要启动HDFS和YARN两个集群. 注意:首次启动HDFS时,必须对其进行格式化操作.本质上是一些清理和准备工作,因为此时的HDFS在物理上还是不存在的. h ...
学习笔记Hadoop（八）—— Hadoop集群的安装与部署（5）—— Hadoop配置参数介绍、Hadoop集群启动与监控
五.Hadoop配置参数介绍 Hadoop集群配置文件主要有: 它们的默认参数配置可以看: core-default.xml :https://hadoop.apache.org/docs/stabl ...
Hadoop集群启动后利用Web界面管理HDFS
Hadoop集群启动后,可以通过自带的浏览器Web界面查看HDFS集群的状态信息,访问IP为NameNode所在服务器的IP地址,hadoop版本为3.0以前访问端口默认为9870,hadoop版本为 ...
Hadoop集群启动Hbase的步骤流程
Hadoop集群启动Hbase的步骤流程系统版本:centOS7.7 HBASE版本:apache-hbase-1.2.1 HADOOP版本:apache-hadoop-2.7.6 JDK版本:jd ...
hadoop 集群启动 ERROR: Cannot write datanode pid /tmp/hadoop-user-datanode.pid. 问题的解决
ERROR: 问题产生原因 1.文件夹权限不够导致 2.磁盘空间不足 3.特殊原因(目录不可用) ERROR: 在配置好Hadoop集群后启动集群产生了如下错误: 提示在写入datanode.pid文 ...
linux 远程权限不够,Eclipse连接远程Hadoop集群开发时权限不足问题解决方案
eclipse连接远程Hadoop集群开发时报错 Exception in thread "main" org.apache.hadoop.security.AccessContr ...
搭建nacos集群启动时，报错Unable to start web server； nested exception is org.springframework.boot.web.server
最近在学习springcloud阿里巴巴的使用,单机使用nacos启动时没有问题,修改了配置之后启动报错,如下 org.springframework.context.ApplicationConte ...

hadoop 集群启动时 Address already in use 解决方法

hadoop 集群启动时 Address already in use 解决方法相关推荐

最新文章

热门文章