[GOBBLIN-1120] Reinitialize HelixManager when Helix participant check throws an exception

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.15.0
• Fix Version/s: 0.15.0
• Component/s: gobblin-cluster
• Assignee: Hung Tran
• Reporter: Sudarshan Vasudevan
• Created: 16/Apr/20 17:05
• Updated: 07/Oct/20 19:11
• Resolved: 07/Oct/20 19:11

Description

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. 

 

Issue Links

• links to: GitHub Pull Request #2960
• links to: https://github.com/apache/incubator-gobblin/pull/2960