分享

有人可以告诉我这个报错日志要怎么解决吗?

小头针 发表于 2015-12-14 18:42:46 [显示全部楼层] 只看大图 回帖奖励 阅读模式 关闭右栏 7 13137
有人可以告诉我这个报错日志要怎么解决吗?
}O0$V2(1NSSLL4{~MK`N768.png

已有(7)人评论

跳转到指定楼层
arsenduan 发表于 2015-12-14 19:51:48
这是配置的HA吗?
journal node出问题了,元数据保存异常了。

回复

使用道具 举报

cranberries8 发表于 2015-12-14 20:54:06
你这是刚开始安装的hadoop集群吧,
看样子你应该是安装ha ,所以你首先确认你的是:
1.你在启动ha之前JournalNode 的进程在不 ,因为 namenode ha 在启动过程中要和 JournalNode 通信
2.如果已经启动了额  确定执行了namenode format 没??  如果没有 那么请执行:hdfs namenode -format

回复

使用道具 举报

小头针 发表于 2015-12-14 21:00:01
cranberries8 发表于 2015-12-14 20:54
你这是刚开始安装的hadoop集群吧,
看样子你应该是安装ha ,所以你首先确认你的是:
1.你在启动ha之前Jou ...

我没有启动JournalNode ,主节点启动了resourceManager、secondaryNamenode、namenode
我格式化了

回复

使用道具 举报

cranberries8 发表于 2015-12-14 21:07:12
小头针 发表于 2015-12-14 21:00
我没有启动JournalNode ,主节点启动了resourceManager、secondaryNamenode、namenode
我格式化了

那你就先执行启动JournalNode  啊 ,这个namenode在 第一次启动时要和启动JournalNode 通信的
回复

使用道具 举报

cranberries8 发表于 2015-12-14 21:08:09
cranberries8 发表于 2015-12-14 21:07
那你就先执行启动JournalNode  啊 ,这个namenode在 第一次启动时要和启动JournalNode 通信的

启动JournalNode的个数一般是3个及以上  (奇数个)
回复

使用道具 举报

小头针 发表于 2015-12-14 21:09:54
cranberries8 发表于 2015-12-14 21:08
启动JournalNode的个数一般是3个及以上  (奇数个)

我的集群式3个节点,一个主的2个从的,可以吧?
回复

使用道具 举报

小头针 发表于 2015-12-14 21:16:06
启动了,我现在运行自带的hadoop-mapreduce-examples-2.5.2.jar 报错了

报错信息如下:麻烦你帮我看一下啦~

2015-12-10 14:46:57,801 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: Updating application attempt appattempt_1449728794696_0002_000002 with final state: FAILED, and exit status: -1000
2015-12-10 14:46:57,801 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: appattempt_1449728794696_0002_000002 State change from ALLOCATED to FINAL_SAVING
2015-12-10 14:46:57,802 INFO org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService: Unregistering app attempt : appattempt_1449728794696_0002_000002
2015-12-10 14:46:57,802 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: appattempt_1449728794696_0002_000002 State change from FINAL_SAVING to FAILED
2015-12-10 14:46:57,803 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Updating application application_1449728794696_0002 with final state: FAILED
2015-12-10 14:46:57,803 INFO org.apache.hadoop.yarn.server.resourcemanager.recovery.RMStateStore: Updating info for app: application_1449728794696_0002
2015-12-10 14:46:57,804 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: application_1449728794696_0002 State change from ACCEPTED to FINAL_SAVING
2015-12-10 14:46:57,804 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Application Attempt appattempt_1449728794696_0002_000002 is done. finalState=FAILED
2015-12-10 14:46:57,804 INFO org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: container_1449728794696_0002_02_000001 Container Transitioned from ACQUIRED to KILLED
2015-12-10 14:46:57,805 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.common.fica.FiCaSchedulerApp: Completed container: container_1449728794696_0002_02_000001 in state: KILLED event:KILL
2015-12-10 14:46:57,805 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=root        OPERATION=AM Released Container        TARGET=SchedulerApp        RESULT=SUCCESS        APPID=application_1449728794696_0002        CONTAINERID=container_1449728794696_0002_02_000001
2015-12-10 14:46:57,805 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerNode: Released container container_1449728794696_0002_02_000001 of capacity <memory:2048, vCores:1> on host slave2:38178, which currently has 0 containers, <memory:0, vCores:0> used and <memory:8192, vCores:8> available, release resources=true
2015-12-10 14:46:57,805 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: default used=<memory:0, vCores:0> numContainers=0 user=root user-resources=<memory:0, vCores:0>
2015-12-10 14:46:57,806 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: completedContainer container=Container: [ContainerId: container_1449728794696_0002_02_000001, NodeId: slave2:38178, NodeHttpAddress: slave2:8042, Resource: <memory:2048, vCores:1>, Priority: 0, Token: Token { kind: ContainerToken, service: 192.168.179.132:38178 }, ] queue=default: capacity=1.0, absoluteCapacity=1.0, usedResources=<memory:0, vCores:0>, usedCapacity=0.0, absoluteUsedCapacity=0.0, numApps=1, numContainers=0 cluster=<memory:16384, vCores:16>
2015-12-10 14:46:57,806 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue: completedContainer queue=root usedCapacity=0.0 absoluteUsedCapacity=0.0 used=<memory:0, vCores:0> cluster=<memory:16384, vCores:16>
2015-12-10 14:46:57,806 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue: Re-sorting completed queue: root.default stats: default: capacity=1.0, absoluteCapacity=1.0, usedResources=<memory:0, vCores:0>, usedCapacity=0.0, absoluteUsedCapacity=0.0, numApps=1, numContainers=0
2015-12-10 14:46:57,806 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Application attempt appattempt_1449728794696_0002_000002 released container container_1449728794696_0002_02_000001 on node: host: slave2:38178 #containers=0 available=8192 used=0 with event: KILL
2015-12-10 14:46:57,806 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Application application_1449728794696_0002 failed 2 times due to Error launching appattempt_1449728794696_0002_000002. Got exception: org.apache.hadoop.yarn.exceptions.YarnException: Unauthorized request to start container.
This token is expired. current time is 1450097708574 found 1449730616554
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at org.apache.hadoop.yarn.api.records.impl.pb.SerializedExceptionPBImpl.instantiateException(SerializedExceptionPBImpl.java:168)
        at org.apache.hadoop.yarn.api.records.impl.pb.SerializedExceptionPBImpl.deSerialize(SerializedExceptionPBImpl.java:106)
        at org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher.launch(AMLauncher.java:122)
        at org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher.run(AMLauncher.java:249)
        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:745)
. Failing the application.
2015-12-10 14:46:57,807 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: application_1449728794696_0002 State change from FINAL_SAVING to FAILED
2015-12-10 14:46:57,807 WARN org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=root        OPERATION=Application Finished - Failed        TARGET=RMAppManager        RESULT=FAILURE        DESCRIPTION=App failed with state: FAILED        PERMISSIONS=Application application_1449728794696_0002 failed 2 times due to Error launching appattempt_1449728794696_0002_000002. Got exception: org.apache.hadoop.yarn.exceptions.YarnException: Unauthorized request to start container.
This token is expired. current time is 1450097708574 found 1449730616554
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at org.apache.hadoop.yarn.api.records.impl.pb.SerializedExceptionPBImpl.instantiateException(SerializedExceptionPBImpl.java:168)
        at org.apache.hadoop.yarn.api.records.impl.pb.SerializedExceptionPBImpl.deSerialize(SerializedExceptionPBImpl.java:106)
        at org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher.launch(AMLauncher.java:122)
        at org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncher.run(AMLauncher.java:249)
        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:745)
. Failing the application.        APPID=application_1449728794696_0002
2015-12-10 14:46:57,808 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAppManager$ApplicationSummary: appId=application_1449728794696_0002,name=QuasiMonteCarlo,user=root,queue=default,state=FAILED,trackingUrl=http://master:18088/cluster/app/application_1449728794696_0002,appMasterHost=N/A,startTime=1449730015871,finishTime=1449730017803,finalStatus=FAILED
2015-12-10 14:46:57,808 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.AppSchedulingInfo: Application application_1449728794696_0002 requests cleared
2015-12-10 14:46:57,810 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: Application removed - appId: application_1449728794696_0002 user: root queue: default #user-pending-applications: 0 #user-active-applications: 0 #queue-pending-applications: 0 #queue-active-applications: 0
2015-12-10 14:46:57,810 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue: Application removed - appId: application_1449728794696_0002 user: root leaf-queue of parent: root #applications: 0
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

关闭

推荐上一条 /2 下一条