分享

Oozie提交作业后,作业被立即挂起

hapjin 发表于 2015-10-10 14:18:35 [显示全部楼层] 只看大图 回帖奖励 阅读模式 关闭右栏 2 19175
本帖最后由 hapjin 于 2015-10-10 16:01 编辑

我在shell命令行提交oozie作业。
ooziejob -oozie http://localhost:11000/oozie -configexamples/apps/map-reduce/job.properties –run  提交成功后,当查询作业的状态时发现作业被
SUSPENDED 了。
在oozie的web界面,查看作业的job log 发现如下信息:大致意思是请求的内存资源超过了Yarn所能分配的最大值,请问各位大神有什么好的建议?这个是Yarn配置资源时配置得太小了,还是自身机器的内存不够(top 命令显示机器的内存是够的)?
2015-10-10 09:51:22,883 INFO org.apache.oozie.command.wf.ActionStartXCommand: SERVER[datanode1] USER[cdhfive] GROUP[-] TOKEN[] APP[map-reduce-wf] JOB[0000001-151009154615306-oozie-oozi-W] ACTION[0000001-151009154615306-oozie-oozi-W@:start:] Start action [0000001-151009154615306-oozie-oozi-W@:start:] with user-retry state : userRetryCount [0], userRetryMax [0], userRetryInterval [10]
2015-10-10 09:51:22,886 INFO org.apache.oozie.command.wf.ActionStartXCommand: SERVER[datanode1] USER[cdhfive] GROUP[-] TOKEN[] APP[map-reduce-wf] JOB[0000001-151009154615306-oozie-oozi-W] ACTION[0000001-151009154615306-oozie-oozi-W@:start:] [***0000001-151009154615306-oozie-oozi-W@:start:***]Action status=DONE
2015-10-10 09:51:22,886 INFO org.apache.oozie.command.wf.ActionStartXCommand: SERVER[datanode1] USER[cdhfive] GROUP[-] TOKEN[] APP[map-reduce-wf] JOB[0000001-151009154615306-oozie-oozi-W] ACTION[0000001-151009154615306-oozie-oozi-W@:start:] [***0000001-151009154615306-oozie-oozi-W@:start:***]Action updated in DB!
2015-10-10 09:51:23,085 INFO org.apache.oozie.command.wf.ActionStartXCommand: SERVER[datanode1] USER[cdhfive] GROUP[-] TOKEN[] APP[map-reduce-wf] JOB[0000001-151009154615306-oozie-oozi-W] ACTION[0000001-151009154615306-oozie-oozi-W@mr-node] Start action [0000001-151009154615306-oozie-oozi-W@mr-node] with user-retry state : userRetryCount [0], userRetryMax [0], userRetryInterval [10]
2015-10-10 09:51:27,578 WARN org.apache.oozie.command.wf.ActionStartXCommand: SERVER[datanode1] USER[cdhfive] GROUP[-] TOKEN[] APP[map-reduce-wf] JOB[0000001-151009154615306-oozie-oozi-W] ACTION[0000001-151009154615306-oozie-oozi-W@mr-node] Error starting action [mr-node]. ErrorType [TRANSIENT], ErrorCode [JA009], Message [JA009: org.apache.hadoop.yarn.exceptions.InvalidResourceRequestException: Invalid resource request, requested memory < 0, or requested memory > max configured, requestedMemory=1536, maxMemory=1225
    at org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.validateResourceRequest(SchedulerUtils.java:203)
    at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.validateAndCreateResourceRequest(RMAppManager.java:377)
    at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.createAndPopulateNewRMApp(RMAppManager.java:320)
    at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.submitApplication(RMAppManager.java:273)
    at org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.submitApplication(ClientRMService.java:574)
    at org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.submitApplication(ApplicationClientProtocolPBServiceImpl.java:213)
    at org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:403)
    at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:619)
    at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1060)
    at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2044)
    at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2040)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:415)
    at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
    at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2038)
]
org.apache.oozie.action.ActionExecutorException: JA009: org.apache.hadoop.yarn.exceptions.InvalidResourceRequestException: Invalid resource request, requested memory < 0, or requested memory > max configured, requestedMemory=1536, maxMemory=1225
    at org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.validateResourceRequest(SchedulerUtils.java:203)
    at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.validateAndCreateResourceRequest(RMAppManager.java:377)
    at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.createAndPopulateNewRMApp(RMAppManager.java:320)
    at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.submitApplication(RMAppManager.java:273)
    at org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.submitApplication(ClientRMService.java:574)
    at org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.submitApplication(ApplicationClientProtocolPBServiceImpl.java:213)
    at org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:403)
    at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:619)
    at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1060)
    at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2044)
    at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2040)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:415)
    at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671)
    at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2038)

    at org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:456)
    at org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:440)
    at org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1008)
    at org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1162)
    at org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
    at org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:64)
    at org.apache.oozie.command.XCommand.call(XCommand.java:286)
    at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:321)
    at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:250)
    at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
    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)
Caused by: java.io.IOException: org.apache.hadoop.yarn.exceptions.InvalidResourceRequestException: Invalid resource request, requested memory < 0, or requested memory > max configured, requestedMemory=1536, maxMemory=1225




yarn-container-mm

yarn-container-mm

yarn-max-scheduler-mm

yarn-max-scheduler-mm

已有(2)人评论

跳转到指定楼层
hapjin 发表于 2015-10-10 16:03:22
原来是Yarn中给 nodemanager 申请分配的内存太小了 ,以及yarn-scheduler.maximum-allocation-mb 指定的内存太小了。。。
把这两个参数加大。即可。。。。
回复

使用道具 举报

arsenduan 发表于 2015-10-10 16:14:24
hapjin 发表于 2015-10-10 16:03
原来是Yarn中给 nodemanager 申请分配的内存太小了 ,以及yarn-scheduler.maximum-allocation-mb 指定的内 ...

container小了
回复

使用道具 举报

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

本版积分规则

关闭

推荐上一条 /2 下一条