[jira] [Resolved] (GOBBLIN-1211) Track unused Helix instances in a thread-safe manner

["Sudarshan Vasudevan (Jira)" <ji...@apache.org>]

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

Sudarshan Vasudevan resolved GOBBLIN-1211.
------------------------------------------
    Resolution: Fixed

> Track unused Helix instances in a thread-safe manner
> ----------------------------------------------------
>
>                 Key: GOBBLIN-1211
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1211
>             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: 40m
>  Remaining Estimate: 0h
>
> The AMRMClient processes container allocation events asynchronously in a separate thread. If there are multiple concurrent container requests and consequent callbacks, we need to ensure that updates to shared data structures such as the set of unused Helix instance names are consistent and thread-safe. In other words, any updates to this set made by one thread will be visible to all other threads handling the container allocation events. 



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