hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhihai xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2315) Should use setCurrentCapacity instead of setCapacity to configure used resource capacity for FairScheduler.
Date Thu, 21 Aug 2014 18:55:14 GMT

    [ https://issues.apache.org/jira/browse/YARN-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105772#comment-14105772
] 

zhihai xu commented on YARN-2315:
---------------------------------

The test error is "java.net.BindException: Address already in use". It is not related to my
patch.
The error may be due to some test resource conflict.

The following is test failure log.

Running org.apache.hadoop.yarn.server.resourcemanager.recovery.TestZKRMStateStoreZKClientConnections
Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.164 sec <<< FAILURE!
- in org.apache.hadoop.yarn.server.resourcemanager.recovery.TestZKRMStateStoreZKClientConnections
testSetZKAcl(org.apache.hadoop.yarn.server.resourcemanager.recovery.TestZKRMStateStoreZKClientConnections)
 Time elapsed: 0.012 sec  <<< ERROR!
java.net.BindException: Address already in use
Running org.apache.hadoop.yarn.server.resourcemanager.TestRMEmbeddedElector
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.923 sec <<< FAILURE!
- in org.apache.hadoop.yarn.server.resourcemanager.TestRMEmbeddedElector
testDeadlockShutdownBecomeActive(org.apache.hadoop.yarn.server.resourcemanager.TestRMEmbeddedElector)
 Time elapsed: 1.746 sec  <<< ERROR!
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: java.net.BindException: Problem binding
to [0.0.0.0:18033] java.net.BindException: Address already in use; For more details see: 
http://wiki.apache.org/hadoop/BindException 

> Should use setCurrentCapacity instead of setCapacity to configure used resource capacity
for FairScheduler.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2315
>                 URL: https://issues.apache.org/jira/browse/YARN-2315
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>         Attachments: YARN-2315.001.patch, YARN-2315.patch
>
>
> Should use setCurrentCapacity instead of setCapacity to configure used resource capacity
for FairScheduler.
> In function getQueueInfo of FSQueue.java, we call setCapacity twice with different parameters
so the first call is overrode by the second call. 
>     queueInfo.setCapacity((float) getFairShare().getMemory() /
>         scheduler.getClusterResource().getMemory());
>     queueInfo.setCapacity((float) getResourceUsage().getMemory() /
>         scheduler.getClusterResource().getMemory());
> We should change the second setCapacity call to setCurrentCapacity to configure the current
used capacity.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message