[ 
https://issues.apache.org/jira/browse/GOBBLIN-1728?focusedWorklogId=818548&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-818548
 ]

ASF GitHub Bot logged work on GOBBLIN-1728:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Oct/22 17:37
            Start Date: 19/Oct/22 17:37
    Worklog Time Spent: 10m 
      Work Description: homatthew commented on code in PR #3586:
URL: https://github.com/apache/gobblin/pull/3586#discussion_r999760735


##########
gobblin-yarn/src/test/java/org/apache/gobblin/yarn/YarnServiceTest.java:
##########
@@ -316,6 +316,7 @@ private static HelixManager getMockHelixManager(Config 
config) {
       
Mockito.when(helixManager.getClusterName()).thenReturn(config.getString(GobblinClusterConfigurationKeys.HELIX_CLUSTER_NAME_KEY));
 
       
Mockito.when(helixManager.getHelixDataAccessor()).thenReturn(helixDataAccessor);
+      
Mockito.when(helixManager.getMetadataStoreConnectionString()).thenReturn("stub");

Review Comment:
   YarnService test doesn't run without this mock. I accidentally broke this 
test in https://github.com/apache/gobblin/pull/3561 but this wasn't caught 
because this test doesn't run in CI due to flakiness and slowness





Issue Time Tracking
-------------------

    Worklog Id:     (was: 818548)
    Time Spent: 1h  (was: 50m)

> Yarn Service requests too many containers due to improper calculation
> ---------------------------------------------------------------------
>
>                 Key: GOBBLIN-1728
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1728
>             Project: Apache Gobblin
>          Issue Type: New Feature
>            Reporter: Matthew Ho
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Yarn Service is responsible for calculating the number of instances based on 
> the helix tasks. Yarn service tracks the number of instances by asking Yarn 
> for the number of resource requests and the number of allocated containers.
>  
> It uses this count to determine if it should ask for more containers or 
> shrink the number of containers. This calculation is currently done 
> improperly and we continue to request containers when we have enough 
> requested.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to