[
https://issues.apache.org/jira/browse/GOBBLIN-1191?focusedWorklogId=444643&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-444643
]
ASF GitHub Bot logged work on GOBBLIN-1191:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Jun/20 00:18
Start Date: 12/Jun/20 00:18
Worklog Time Spent: 10m
Work Description: sv2000 opened a new pull request #3039:
URL: https://github.com/apache/incubator-gobblin/pull/3039
… by Gobblin Application Master
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
- [x] My PR addresses the following [Gobblin
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-1191
### Description
- [x] Here are some details about my PR, including screenshots (if
applicable):
Currently, when containers are released by Gobblin Application Master, the
Helix instance names are not released back to the pool of unused instance
names. The effect of this is that the number of unique Helix instances keeps
growing over time. Since Helix creates one znode per instance, this can result
in the number of znodes to grow unboundedly.
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [x] 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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 444643)
Remaining Estimate: 0h
Time Spent: 10m
> Reuse Helix instance names when containers are released by Gobblin
> Application Master
> -------------------------------------------------------------------------------------
>
> Key: GOBBLIN-1191
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1191
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-yarn
> Affects Versions: 0.15.0
> Reporter: Sudarshan Vasudevan
> Assignee: Abhishek Tiwari
> Priority: Major
> Fix For: 0.15.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, when containers are released by Gobblin Application Master, the
> Helix instance names are not released back to the pool of unused instance
> names. The effect of this is that the number of unique Helix instances keeps
> growing over time. Since Helix creates one znode per instance, this can
> result in the number of znodes to grow unboundedly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
