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:05:00 UTC
[jira] [Updated] (GOBBLIN-1120) Reinitialize HelixManager when
Helix participant check throws an exception
[ https://issues.apache.org/jira/browse/GOBBLIN-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudarshan Vasudevan updated GOBBLIN-1120:
-----------------------------------------
Fix Version/s: 0.15.0
> Reinitialize HelixManager when Helix participant check throws an exception
> --------------------------------------------------------------------------
>
> Key: GOBBLIN-1120
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1120
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-cluster
> Affects Versions: 0.15.0
> Reporter: Sudarshan Vasudevan
> Assignee: Hung Tran
> Priority: Major
> Fix For: 0.15.0, 0.16.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When the underlying ZkClient is closed, Helix participant check throws:
> Caused by: java.lang.IllegalStateException: ZkClient already closed!
> In these cases, the HelixManager instance used to do the participant check needs to be re-initialized to obtain a new ZKClient.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)