hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bibin A Chundatt (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-6317) Invalid Resource Exception could be handled properly when cores not available
Date Sat, 11 Jul 2015 19:06:04 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bibin A Chundatt resolved MAPREDUCE-6317.
-----------------------------------------
    Resolution: Duplicate

Fixed as part of https://issues.apache.org/jira/browse/MAPREDUCE-5279

> Invalid Resource Exception could be handled properly when cores not available
> -----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6317
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6317
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster, mr-am
>         Environment: 1 RM , 1 DN
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>            Priority: Minor
>
> Configure yarn.nodemanager.resource.cpu-vcores=2 for NM
> Set mapreduce.map.cpu.vcores=5 while running sleep job n client
> {code}
> 2015-04-10 20:37:26,111 ERROR [RMCommunicator Allocator] org.apache.hadoop.mapreduce.v2.app.rm.RMCommunicator:
ERROR IN CONTACTING RM. 
> org.apache.hadoop.yarn.exceptions.InvalidResourceRequestException: Invalid resource request,
requested virtual cores < 0, or requested virtual cores > max configured, requestedVirtualCores=5,
maxVirtualCores=2
> 	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.validateResourceRequest(SchedulerUtils.java:213)
> 	at org.apache.hadoop.yarn.server.resourcemanager.RMServerUtils.validateResourceRequests(RMServerUtils.java:97)
> 	at org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService.allocate(ApplicationMasterService.java:502)
> 	at org.apache.hadoop.yarn.api.impl.pb.service.ApplicationMasterProtocolPBServiceImpl.allocate(ApplicationMasterProtocolPBServiceImpl.java:60)
> 	at org.apache.hadoop.yarn.proto.ApplicationMasterProtocol$ApplicationMasterProtocolService$2.callBlockingMethod(ApplicationMasterProtocol.java:99)
> 	at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:636)
> 	at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:976)
> 	at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2142)
> 	at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2138)
> 	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:1669)
> 	at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2136)
> 	at sun.reflect.GeneratedConstructorAccessor17.newInstance(Unknown Source)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> 	at org.apache.hadoop.yarn.ipc.RPCUtil.instantiateException(RPCUtil.java:53)
> 	at org.apache.hadoop.yarn.ipc.RPCUtil.unwrapAndThrowException(RPCUtil.java:101)
> 	at org.apache.hadoop.yarn.api.impl.pb.client.ApplicationMasterProtocolPBClientImpl.allocate(ApplicationMasterProtocolPBClientImpl.java:79)
> 	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:186)
> 	at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:101)
> 	at com.sun.proxy.$Proxy34.allocate(Unknown Source)
> 	at org.apache.hadoop.mapreduce.v2.app.rm.RMContainerRequestor.makeRemoteRequest(RMContainerRequestor.java:199)
> 	at org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.getResources(RMContainerAllocator.java:686)
> 	at org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.heartbeat(RMContainerAllocator.java:257)
> 	at org.apache.hadoop.mapreduce.v2.app.rm.RMCommunicator$1.run(RMCommunicator.java:281)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: 2015-04-10 20:37:27,117 ERROR [RMCommunicator Allocator] org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator:
Could not contact RM after 360000 milliseconds.
> 2015-04-10 20:37:27,173 ERROR [RMCommunicator Allocator] org.apache.hadoop.mapreduce.v2.app.rm.RMCommunicator:
Error communicating with RM: Could not contact RM after 360000 milliseconds.
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Could not contact RM after 360000
milliseconds.
> 	at org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.getResources(RMContainerAllocator.java:712)
> 	at org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.heartbeat(RMContainerAllocator.java:257)
> 	at org.apache.hadoop.mapreduce.v2.app.rm.RMCommunicator$1.run(RMCommunicator.java:281)
> 	at java.lang.Thread.run(Thread.java:745)
> {code}
> Rm communication timeout is thrown and fails after 2 app attempts
> Invalid resource exception not handled in RM container allocator
> {code}
>     @SuppressWarnings("unchecked")
>   private List<Container> getResources() throws Exception {
>     applyConcurrentTaskLimits();
>     // will be null the first time
>     Resource headRoom =
>         getAvailableResources() == null ? Resources.none() :
>             Resources.clone(getAvailableResources());
>     AllocateResponse response;
>     /*
>      * If contact with RM is lost, the AM will wait MR_AM_TO_RM_WAIT_INTERVAL_MS
>      * milliseconds before aborting. During this interval, AM will still try
>      * to contact the RM.
>      */
>     try {
>       response = makeRemoteRequest();
>       // Reset retry count if no exception occurred.
>       retrystartTime = System.currentTimeMillis();
>     } catch (ApplicationAttemptNotFoundException e ) {
> {code}
> RMContainerAllocator should handle invalid resource exception and wait till new nodemanager
added with expected resource



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message