You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/06 00:13:00 UTC

[jira] [Work logged] (GOBBLIN-1072) Being more conservative on releasing YARN containers

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

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

                Author: ASF GitHub Bot
            Created on: 06/Mar/20 00:12
            Start Date: 06/Mar/20 00:12
    Worklog Time Spent: 10m 
      Work Description: autumnust commented on pull request #2912: [GOBBLIN-1072] Add sliding window to protect AutoScaling from fluctuation of number of active Helix partitions
URL: https://github.com/apache/incubator-gobblin/pull/2912
 
 
   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   
   ### JIRA
   - https://issues.apache.org/jira/browse/GOBBLIN-1072
   
   
   ### Description
   - An additional data structure `MaxValueEvictingQueue` to wrap multiple instances of `numTargetContainers` and behaved like an sliding-window where we could fetch the maxValue in the sliding-window in constant time. 
   - The advantage of this data structure is, if there's fluctuation in the number of active Helix partitions, a single fluctuation wont't impact the number of containers we requested in `YarnService`. 
   - The sliding-window's size is defined by the number of attempts that we query Helix for getting partitions number. 
   
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   
   ### Commits
   - [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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

            Worklog Id:     (was: 398778)
    Remaining Estimate: 0h
            Time Spent: 10m

> Being more conservative on releasing YARN containers
> ----------------------------------------------------
>
>                 Key: GOBBLIN-1072
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1072
>             Project: Apache Gobblin
>          Issue Type: Improvement
>            Reporter: Lei Sun
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)