You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Eric Badger (JIRA)" <ji...@apache.org> on 2017/02/23 19:29:44 UTC
[jira] [Comment Edited] (YARN-4954)
TestYarnClient.testReservationAPIs fails on machines with less than 4 GB
available memory
[ https://issues.apache.org/jira/browse/YARN-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881074#comment-15881074 ]
Eric Badger edited comment on YARN-4954 at 2/23/17 7:29 PM:
------------------------------------------------------------
[~leftnoteasy], YARN-5389 fixed the timeout failures related to the NMs not heartbeating quickly enough to update the RM's capacity. But this JIRA is more about the requests being too high in general. I can't get this test to fail anymore locally and I have forgotten how exactly it was failing for me in the past. I might be getting Jiras mixed up in my head, but I remember something about capacities being updated in different places and not propagating quickly enough once we got past the test check. However, that doesn't seem to be mentioned here, so it is quite possible that I'm thinking of a different Jira.
[~GergelyNovak] addressed the issue of machines/VMs with less than 4GB of memory and confirmed that it still worked, so I'll take his word for it. I'm ok closing this and reopening if the issue shows again.
Edit: Pretty sure the Jira I'm mixing this one up with about the capacity not getting propagated is YARN-5994
was (Author: ebadger):
[~leftnoteasy], YARN-5389 fixed the timeout failures related to the NMs not heartbeating quickly enough to update the RM's capacity. But this JIRA is more about the requests being too high in general. I can't get this test to fail anymore locally and I have forgotten how exactly it was failing for me in the past. I might be getting Jiras mixed up in my head, but I remember something about capacities being updated in different places and not propagating quickly enough once we got past the test check. However, that doesn't seem to be mentioned here, so it is quite possible that I'm thinking of a different Jira.
[~GergelyNovak] addressed the issue of machines/VMs with less than 4GB of memory and confirmed that it still worked, so I'll take his word for it. I'm ok closing this and reopening if the issue shows again.
> TestYarnClient.testReservationAPIs fails on machines with less than 4 GB available memory
> -----------------------------------------------------------------------------------------
>
> Key: YARN-4954
> URL: https://issues.apache.org/jira/browse/YARN-4954
> Project: Hadoop YARN
> Issue Type: Test
> Components: test
> Affects Versions: 3.0.0-alpha1
> Reporter: Gergely Novák
> Assignee: Gergely Novák
> Priority: Critical
> Attachments: YARN-4954.001.patch, YARN-4954.002.patch
>
>
> TestYarnClient.testReservationAPIs sometimes fails with this error:
> {noformat}
> java.lang.AssertionError: org.apache.hadoop.yarn.server.resourcemanager.reservation.exceptions.PlanningException: The request cannot be satisfied
> at org.apache.hadoop.yarn.ipc.RPCUtil.getRemoteException(RPCUtil.java:38)
> at org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.submitReservation(ClientRMService.java:1254)
> at org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.submitReservation(ApplicationClientProtocolPBServiceImpl.java:457)
> at org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:515)
> at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:637)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:989)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2422)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2418)
> 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:1742)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2416)
> Caused by: org.apache.hadoop.yarn.server.resourcemanager.reservation.exceptions.PlanningException: The request cannot be satisfied
> at org.apache.hadoop.yarn.server.resourcemanager.reservation.planning.IterativePlanner.computeJobAllocation(IterativePlanner.java:151)
> at org.apache.hadoop.yarn.server.resourcemanager.reservation.planning.PlanningAlgorithm.allocateUser(PlanningAlgorithm.java:64)
> at org.apache.hadoop.yarn.server.resourcemanager.reservation.planning.PlanningAlgorithm.createReservation(PlanningAlgorithm.java:140)
> at org.apache.hadoop.yarn.server.resourcemanager.reservation.planning.TryManyReservationAgents.createReservation(TryManyReservationAgents.java:55)
> at org.apache.hadoop.yarn.server.resourcemanager.reservation.planning.AlignedPlannerWithGreedy.createReservation(AlignedPlannerWithGreedy.java:84)
> at org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.submitReservation(ClientRMService.java:1237)
> ... 10 more
> at org.junit.Assert.fail(Assert.java:88)
> at org.apache.hadoop.yarn.client.api.impl.TestYarnClient.testReservationAPIs(TestYarnClient.java:1227)
> {noformat}
> This is caused by really not having enough available memory to complete the reservation (4 * 1024 MB). In my opinion lowering the required memory (either by lowering the number of containers to 2, or the memory to 512 MB) would make the test more stable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org