You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Sudarshan Vasudevan (Jira)" <ji...@apache.org> on 2020/10/07 19:00:00 UTC

[jira] [Updated] (GOBBLIN-1191) Reuse Helix instance names when containers are released by Gobblin Application Master

     [ https://issues.apache.org/jira/browse/GOBBLIN-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudarshan Vasudevan updated GOBBLIN-1191:
-----------------------------------------
    Fix Version/s:     (was: 0.16.0)
                   0.15.0

> 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: 1h 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)