日韩性视频-久久久蜜桃-www中文字幕-在线中文字幕av-亚洲欧美一区二区三区四区-撸久久-香蕉视频一区-久久无码精品丰满人妻-国产高潮av-激情福利社-日韩av网址大全-国产精品久久999-日本五十路在线-性欧美在线-久久99精品波多结衣一区-男女午夜免费视频-黑人极品ⅴideos精品欧美棵-人人妻人人澡人人爽精品欧美一区-日韩一区在线看-欧美a级在线免费观看

歡迎訪問 生活随笔!

生活随笔

當前位置: 首頁 > 编程资源 > 编程问答 >内容正文

编程问答

Hadoop常见异常

發(fā)布時間:2024/1/23 编程问答 33 豆豆
生活随笔 收集整理的這篇文章主要介紹了 Hadoop常见异常 小編覺得挺不錯的,現(xiàn)在分享給大家,幫大家做個參考.

Hadoop常見異常

@(HADOOP)[hadoop]

  • Hadoop常見異常
    • 1ShellExitCodeException
    • 2libhadoopso100 which might have disabled stack guard
    • 3Retrying connect to server master16610252481669000 Already tried 0 times
    • 4Permission denied userliaoliuqing accessWRITE inodejediaelsupergrouprwxr-xr-x
    • 5Incompatible namespaceIDs

1、Shell$ExitCodeException

現(xiàn)象:運行hadoop job時出現(xiàn)如下異常:

14/07/09 14:42:50 INFO mapreduce.Job: Task Id : attempt_1404886826875_0007_m_000000_1, Status : FAILED Exception from container-launch: org.apache.hadoop.util.Shell$ExitCodeException: org.apache.hadoop.util.Shell$ExitCodeException: at org.apache.hadoop.util.Shell.runCommand(Shell.java:505)at org.apache.hadoop.util.Shell.run(Shell.java:418)at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:650)at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:195)at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:300)at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:81)at java.util.concurrent.FutureTask.run(FutureTask.java:262)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:744)Container exited with a non-zero exit code 1

原因及解決辦法:原因未知。重啟可恢復正常

2、libhadoop.so.1.0.0 which might have disabled stack guard

現(xiàn)象:Hadoop 2.2.0 - warning: You have loaded library /home/hadoop/2.2.0/lib/native/libhadoop.so.1.0.0 which might have disabled stack guard.
原因及解決方法:
在/etc/profile中添加:

#hadoop configuration export PATH=$PATH:/home/jediael/hadoop-2.4.1/bin:/home/jediael/hadoop-2.4.1/sbin export HADOOP_HOME=/home/jediael/hadoop-2.4.1 export HADOOP_COMMON_HOME=$HADOOP_HOME export HADOOP_HDFS_HOME=$HADOOP_HOME export HADOOP_MAPRED_HOME=$HADOOP_HOME export HADOOP_YARN_HOME=$HADOOP_HOME export HADOOP_CONF_DIR=$HADOOP_HOME/etc/hadoop export HADOOP_COMMON_LIB_NATIVE_DIR=$HADOOP_HOME/lib/native export HADOOP_OPTS="-Djava.library.path=$HADOOP_HOME/lib"

此警告出現(xiàn)的原因是最后2項未添加。

3、Retrying connect to server: master166/10.252.48.166:9000. Already tried 0 time(s)

在datanode上執(zhí)行hdfs相關(guān)命令時,出現(xiàn)以下錯誤:

[jediael@slave156 ~]$ hadoop fs -ls / 14/08/31 15:00:37 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) 14/08/31 15:00:38 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) 14/08/31 15:00:39 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) 14/08/31 15:00:40 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) 14/08/31 15:00:41 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) 14/08/31 15:00:42 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 5 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) 14/08/31 15:00:43 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 6 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) 14/08/31 15:00:44 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 7 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) 14/08/31 15:00:45 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 8 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) 14/08/31 15:00:46 INFO ipc.Client: Retrying connect to server: master166/10.252.48.166:9000. Already tried 9 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) ls: Call to master166/10.252.48.166:9000 failed on connection exception: java.net.ConnectException: Connection refused

出現(xiàn)以上錯誤,通常都是由于datanode無法連接到namenode所致,以下是一種情況:

/etc/hosts中存在127.0.0.1 *的配置,如

127.0.0.1 localhost

將這些配置去掉,然后重新格式化namenode,并重啟hadoop進程即可解決。

或者是以下原因:

hadoop安裝完成后,必須要用haddop namenode format格式化后,才能使用,如果重啟機器

在啟動hadoop后,用hadoop fs -ls命令老是報 10/09/25 18:35:29 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9000. Already tried 0 time(s).的錯誤,

用jps命令,也看不不到namenode的進程, 必須再用命令hadoop namenode format格式化后,才能再使用

原因是:hadoop默認配置是把一些tmp文件放在/tmp目錄下,重啟系統(tǒng)后,tmp目錄下的東西被清除,所以報錯

解決方法:在conf/core-site.xml 中增加以下內(nèi)容

<property><name>hadoop.tmp.dir</name><value>/var/log/hadoop/tmp</value><description>A base for other temporary directories</description></property>

重啟hadoop后,格式化namenode即可

4、Permission denied: user=liaoliuqing, access=WRITE, inode=”“:jediael:supergroup:rwxr-xr-x

原因為用戶權(quán)限不足,能能訪寫HDFS中的文件。

解決方案:

關(guān)閉hadoop權(quán)限,在hdfs-site.xml文件中添加

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

5、Incompatible namespaceIDs

2015-02-02 15:10:57,526 INFO org.apache.hadoop.metrics2.impl.MetricsConfig: loaded properties from hadoop-metrics2.properties 2015-02-02 15:10:57,543 INFO org.apache.hadoop.metrics2.impl.MetricsSourceAdapter: MBean for source MetricsSystem,sub=Stats registered. 2015-02-02 15:10:57,543 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period at 10 second(s). 2015-02-02 15:10:57,544 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: DataNode metrics system started 2015-02-02 15:10:57,699 INFO org.apache.hadoop.metrics2.impl.MetricsSourceAdapter: MBean for source ugi registered. 2015-02-02 15:10:58,090 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: java.io.IOException: Incompatible namespaceIDs in /mnt/tmphadoop/dfs/data: namenode namespaceID = 2017454015; datanode namespaceID = 1238467850at org.apache.hadoop.hdfs.server.datanode.DataStorage.doTransition(DataStorage.java:232)at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead(DataStorage.java:147)at org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:414)at org.apache.hadoop.hdfs.server.datanode.DataNode.<init>(DataNode.java:321)at org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:1712)at org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:1651)at org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:1669)at org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:1795)at org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:1812)

問題原因:
每次namenode format會重新創(chuàng)建一個namenodeId,而${hadoop.tmp.dir}/dfs/data下包含了上次format下的id,當重新執(zhí)行namenode format時清空了namenode下的數(shù)據(jù),但是沒有清空datanode下的數(shù)據(jù),所以造成namenode節(jié)點上的namespaceID與 datanode節(jié)點上的namespaceID不一致,從而導致從現(xiàn)上述異常,啟動失敗。

解決辦法:
(1)停止hadoop

stop-all.sh

(2)在各個slave中刪除dfs.data.dir中的內(nèi)容。若此屬性未修改,則其默認值為

<property><name>${dfs.data.dir}</name><value>${hadoop.tmp.dir}/dfs/data</value><description>Determines where on the local filesystem an DFS data nodeshould store its blocks. If this is a comma-delimitedlist of directories, then data will be stored in all nameddirectories, typically on different devices.Directories that do not exist are ignored.</description> </property>

(3)重新格式化namenode

hadoop namenode -format

然后start-all.sh啟動hadoop

以上解決辦法需要將原有數(shù)據(jù)刪除,若數(shù)據(jù)不能刪除,則使用以下方法之一:
(1)修改dfs.data.dir/current/VERSIONdatanodeidnamenodeid2{dfs.data.dir}

總結(jié)

以上是生活随笔為你收集整理的Hadoop常见异常的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯,歡迎將生活随笔推薦給好友。